Skip to main content
Glama

Opus Growth, Ad Platforms MCP Connector

Create Meta Lead Form

create_meta_lead_form

Creates an INSTANT FORM (lead form) on a Facebook Page, with custom questions, and returns the form id to attach to a lead ad. questions: each entry is EITHER a standard field Meta pre-fills from the user's profile — FULL_NAME, FIRST_NAME, LAST_NAME, EMAIL, PHONE, CITY, COMPANY_NAME, JOB_TITLE, DOB, GENDER … — OR a custom question written as 'Question text?|Option 1|Option 2' (with options it renders as a choice list, without options it is a free-text answer). privacy_policy_url is REQUIRED by Meta on every form. Optional: intro_headline / intro_description (the card shown before the questions), thank_you_text, follow_up_url (where the thank-you button goes). locale is the form's language (default TR) — give it in Meta's full form, e.g. EN_US, EN_GB, DE_DE, AR_AR; it sets BOTH Meta's own interface strings AND the three texts this tool supplies for you (the privacy-policy link text and the intro-card / thank-you buttons), so an EN_US form reads "Privacy Policy" / "Continue" / "Go to site". confirm=false shows those three under form_button_texts, so you can check the language before the form exists. higher_intent=true creates a 'Higher intent' Instant Form (Meta's is_optimized_for_quality — it adds a review/confirm step before submission, giving fewer but more qualified leads); the default is 'More volume'. Meta does NOT allow the form type to change after the form is published, so choose it at creation, and note Meta's API cannot create a form as an unpublished draft — use confirm=false to preview the fields (and see form_type) before it exists. After creating it, build the ad with create_meta_link_ad(..., lead_gen_form_id=) on an ad set whose optimization_goal is LEAD_GENERATION and whose promoted_object page_id is this Page. confirm=false = preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
localeNoTR
confirmNo
page_idYes
questionsYes
follow_up_urlNo
higher_intentNo
intro_headlineNo
thank_you_textNo
intro_descriptionNo
privacy_policy_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. Added
  12. Removed
  13. Added
  14. Removed
  15. Added
  16. Removed
  17. Added
  18. Removed
  19. Added
  20. Removed
  21. Added
  22. Removed
  23. Added
  24. Removed
  25. Added
  26. Removed
  27. Added
  28. Removed
  29. Added
  30. Removed
  31. Added
  32. Removed
  33. Added
  34. Removed
  35. Added
  36. Removed
  37. Added
  38. Removed
  39. Added

TDQS

A4.7/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: Meta requires privacy_policy_url, Meta's API cannot create an unpublished draft, form type is immutable once published, higher_intent adds a review step and trades volume for quality. Doesn't address auth/permission requirements or rate limits, so not a full 5.

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

Conciseness4/5

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

Front-loads the core action, but the flow is dense and the trailing 'confirm=false = preview' is stated twice, which is minor redundancy. For an 11-parameter tool with nontrivial semantics, the length is largely justified.

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

Completeness5/5

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

Covering a mutation tool with 11 params, no schema descriptions, and an output schema present, the description supplies the return id, the confirm=false preview behavior, and the form_button_texts preview, so an agent has everything needed to call and chain it.

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

Parameters5/5

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

With 0% schema coverage the description carries the full burden and mostly delivers: the questions format (standard field OR 'text?|opt1|opt2'), privacy_policy_url being required, locale syntax with concrete examples and its dual effect on interface and supplied button texts, and the meaning of confirm/higher_intent. Only name and page_id are left undocumented, which are self-evident.

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?

States a specific verb and resource ('Creates an INSTANT FORM (lead form) on a Facebook Page') and adds the return value (form id) that an agent needs to chain into ad creation. It is clearly distinguishable from list_meta_lead_forms and from the platform-generic create_lead_form sibling.

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

Usage Guidelines5/5

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

Explicitly routes usage: use confirm=false to preview before the form exists, choose higher_intent at creation because Meta forbids changing form type after publish, and attach the returned id via create_meta_link_ad with optimization_goal LEAD_GENERATION. Both when-to-use and constraints are stated rather than implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.