Skip to main content
Glama

meta_ads_lead_forms_create

Create a Facebook lead form for Meta Ads. Add custom questions to capture lead data. Privacy policy URL required. Returns new form ID.

Instructions

Creates a new lead form on a Facebook Page. Returns the new form_id. Mutating, reversible via rollback_apply (rollback archives the form rather than deleting submitted leads). Questions is an ordered list of standard Meta types (FULL_NAME, EMAIL, PHONE_NUMBER, COMPANY_NAME, JOB_TITLE, CITY, STATE, ZIP_CODE, COUNTRY, DATE_OF_BIRTH) or CUSTOM (requires key, label, and options for dropdowns). Meta requires a privacy_policy_url by policy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNoMeta Ads account ID in the format 'act_XXXXXXXXXX' (e.g. 'act_1234567890'). Optional — falls back to META_ADS_ACCOUNT_ID from the configured credentials. The leading 'act_' prefix is required.
page_idYesFacebook Page ID that will own the form.
nameYesForm name shown in Ads Manager and Page Lead Center.
questionsYesOrdered question list. Standard-type questions only need `type`; CUSTOM questions require `key`, `label`, and (for dropdowns) `options`.
privacy_policy_urlYesHTTPS URL of the advertiser's privacy policy. Required by Meta policy — forms without one are rejected.
follow_up_action_urlNoOptional URL the user is redirected to after submission (e.g. thank-you page). Omit to show Meta's default confirmation only. Superseded by thank_you_page when both are supplied.
localeNoOptional form locale (e.g. ``ja_JP``). Defaults to the Page's primary locale.
context_cardNoOptional intro / welcome screen shown before the form. Lifts conversion rate measurably when supplied. Expected keys: title, content, style (PARAGRAPH_STYLE or LIST_STYLE), cover_photo_id.
thank_you_pageNoOptional custom completion screen with a CTA. Replaces follow_up_action_url's simple redirect when supplied. Expected keys: title, body, button_type (VIEW_WEBSITE / CALL_BUSINESS / MESSAGE_BUSINESS / DOWNLOAD / DOWNLOAD_APP), website_url, button_text.
is_higher_intentNoWhen true, Meta renders a 3-step form (input → review → submit) which trims junk submissions at the cost of total leads volume. Default false (single-step).
conditional_questions_choicesNoBranching logic — given a prior question's value, choose which question to ask next. Each entry: {question: <key>, value: <choice>, next_question_key: <key>}. Meta validates the keys refer to real questions.
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It discloses mutation, reversibility via rollback_apply, and the privacy policy requirement. It adds context like the archiving behavior and the conversion rate lift of context cards, but could mention rate limits or auth needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficiently front-loaded with the core purpose, return, and mutability. Every sentence provides essential information without redundancy. The question parameter summary is dense but necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 11 parameters, nested objects, and no output schema, the description covers the main purpose, return, key constraints (privacy_policy_url), and parameter semantics. However, it could be more thorough on error handling or the structure of context_card and thank_you_page.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3. The description adds value beyond schema by explaining question types concisely, noting that follow_up_action_url is superseded by thank_you_page, and stating the conversion rate impact of context_card.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it creates a new lead form on a Facebook Page, returns the form_id, and is mutating and reversible. This distinguishes it from sibling tools like get, list, update, and duplicate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for creating new lead forms but does not explicitly state when to use this tool over alternatives (e.g., update for modifying existing forms). No exclusions or alternative tool names are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logly/mureo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server