Get Meta Lead Form Submissions
User wants to see lead submissions, lead data, or leads collected from a Meta lead form.
Retrieves individual lead submissions for a specific lead form, including contact details and associated ad/campaign information.
When to use this tool:
- “Show me the leads from form X”
- “Get my lead form submissions”
- “Download my Meta leads”
- “Show lead data from my campaign”
- “How many leads did I get?”
Returns per lead:
- Submission timestamp
- Field data (name, email, phone, etc. — varies by form)
- Source: organic or paid (with campaign name and ad name)
- Lead ID
Parameters:
- form_id: Lead form ID (required — get from list_meta_lead_forms)
- ad_account_id: Required for multi-account users. Get from list_connected_accounts
- limit: Maximum leads to return (default: 100)
Permission: Requires ‘leads_retrieval’ scope. If the user gets a permission error, they need to disconnect and reconnect their Meta account to grant the updated permissions.
Execution time: 2-5 seconds Data source: Meta Marketing API (live)
Authorizations
API key from https://adspirer.ai/keys. Prefix sk_live_. Treat as a secret — never commit.
Headers
Client-generated UUID to make writes idempotent. Strongly recommended for write tools. A repeat call with the same key returns the cached result instead of re-executing. Example: 550e8400-e29b-41d4-a716-446655440000
Body
All tool arguments are wrapped in an arguments object. The fields accepted inside arguments are listed below — required fields are marked with a red asterisk.
Input schema for retrieving lead form submissions.
Response
Tool executed successfully. data.text carries the human-readable result (markdown-friendly). data.quota shows your current usage against the plan limit. data.structured appears when the tool emits machine-parseable structured content. data.content appears for tools that return non-text blocks (images, resources).
Returned on HTTP 200. data.text is the primary human-readable output. data.quota is always present for billable calls. data.structured is set only when the tool emits machine-parseable structured content. data.content is set only when the tool emits non-text content blocks.

