Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

meta_ads_lead_forms_create

Create a Facebook lead form on a Page by specifying questions, privacy policy, and follow-up URLs. Returns the new form ID for use in ads.

Instructions

Creates a new lead form on a Facebook Page. Returns the new form_id. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. 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 both privacy_policy_url and follow_up_action_url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesForm name shown in Ads Manager and Page Lead Center.
localeNoOptional form locale (e.g. ``ja_JP``). Defaults to the Page's primary locale.
page_idYesFacebook Page ID that will own the form.
questionsYesOrdered question list. Standard-type questions only need `type`; CUSTOM questions require `key`, `label`, and (for dropdowns) `options`.
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.
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. cover_photo_id is a PAGE photo id picked from meta_ads_pages_photos_list and is write-only: Meta reads it back as context_card.cover_photo.id ({id, created_time}), and asking for context_card{cover_photo_id} is rejected.
thank_you_pageNoOptional custom completion screen with a CTA. Richer than follow_up_action_url's plain redirect, but does not replace it — Meta still requires follow_up_action_url. 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).
privacy_policy_urlYesHTTPS URL of the advertiser's privacy policy. Required by Meta policy — forms without one are rejected.
follow_up_action_urlYesURL the user is sent to from the completion screen (e.g. thank-you page). Required by Meta — omitting it fails with error_subcode 1892085 'Missing field(s): FollowUpActionURL'. thank_you_page adds a richer completion screen but does not replace this field.
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.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.15.0
    • changedInput schema / properties / context_card / description
      Previous value: -"Optional 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. cover_photo_id is a PAGE photo id from meta_ads_pages_upload_photo and is write-only: Meta reads it back as context_card.cover_photo.id ({id, created_time}), and asking for context_card{cover_photo_id} is rejected."New value: +"Optional 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. cover_photo_id is a PAGE photo id picked from meta_ads_pages_photos_list and is write-only: Meta reads it back as context_card.cover_photo.id ({id, created_time}), and asking for context_card{cover_photo_id} is rejected."
  2. Changed4 schema fields changedv0.10.44
    • changedInput schema / properties / context_card / description
      Previous value: -"Optional 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."New value: +"Optional 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. cover_photo_id is a PAGE photo id from meta_ads_pages_upload_photo and is write-only: Meta reads it back as context_card.cover_photo.id ({id, created_time}), and asking for context_card{cover_photo_id} is rejected."
    • changedInput schema / properties / follow_up_action_url / description
      Previous value: -"Optional 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."New value: +"URL the user is sent to from the completion screen (e.g. thank-you page). Required by Meta — omitting it fails with error_subcode 1892085 'Missing field(s): FollowUpActionURL'. thank_you_page adds a richer completion screen but does not replace this field."
    • changedInput schema / properties / thank_you_page / description
      Previous value: -"Optional 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."New value: +"Optional custom completion screen with a CTA. Richer than follow_up_action_url's plain redirect, but does not replace it — Meta still requires follow_up_action_url. Expected keys: title, body, button_type (VIEW_WEBSITE / CALL_BUSINESS / MESSAGE_BUSINESS / DOWNLOAD / DOWNLOAD_APP), website_url, button_text."
    • changedInput schema / required
      Previous value: -[
-  "page_id",
-  "name",
-  "questions",
-  "privacy_policy_url"
-]New value: +[
+  "page_id",
+  "name",
+  "questions",
+  "privacy_policy_url",
+  "follow_up_action_url"
+]
  3. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  4. Changed6 schema fields changedv0.9.17
    • addedInput schema / properties / conditional_questions_choices
      Added value: +{
+  "description": "Branching 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.",
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / context_card
      Added value: +{
+  "description": "Optional 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.",
+  "type": "object"
+}
    • changedInput schema / properties / follow_up_action_url / description
      Previous value: -"Optional URL the user is redirected to after submission (e.g. thank-you page). Omit to show Meta's default confirmation only."New value: +"Optional 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."
    • addedInput schema / properties / is_higher_intent
      Added value: +{
+  "description": "When 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).",
+  "type": "boolean"
+}
    • addedInput schema / properties / locale
      Added value: +{
+  "description": "Optional form locale (e.g. ``ja_JP``). Defaults to the Page's primary locale.",
+  "type": "string"
+}
    • addedInput schema / properties / thank_you_page
      Added value: +{
+  "description": "Optional 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.",
+  "type": "object"
+}
  5. Addedv0.9.12
  6. Removedv0.9.6
  7. Addedv0.9.2
  8. Removedv0.9.1
  9. Addedv1.0.5

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden, and it discloses the most decision-relevant trait: mutation with irreversibility, plus a concrete mitigation path (mureo_state_action_log_append). It also discloses the return value and the two required-by-Meta fields. It doesn't cover auth needs or failure modes, but the critical behavioral context is present and there is no contradiction with annotations (none exist).

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?

Four dense sentences, front-loaded with the core purpose and mutation warning, followed by the question-format constraint and Meta requirements. Slight redundancy: the enumerated standard question types repeat what the schema's type property already documents. Still, every sentence earns its place and nothing is bloated.

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?

The schema is rich (100% field coverage, nested objects like context_card and conditional_questions_choices documented with behavioral quirks), so the description need only add cross-cutting context — which it does: the return value (compensating for the missing output schema) and rollback guidance. A brief pointer toward advanced options (context_card, conditional branching, is_higher_intent) would push this to a 5, but nothing critical is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline of 3 applies. The description adds the 'ordered list' nuance for questions and reiterates the required URL fields, but the schema already documents every parameter in depth (including the full list of standard question types, write-only behavior of cover_photo_id, and the error_subcode for a missing follow_up_action_url). The description's added value over the schema is modest.

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 states a specific verb+resource: 'Creates a new lead form on a Facebook Page', and names the return value (form_id). This unambiguously distinguishes it from the lead-form sibling tools (meta_ads_lead_forms_list, meta_ads_lead_forms_get, meta_ads_lead_forms_update, meta_ads_lead_forms_duplicate) without needing to open the schema.

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

Usage Guidelines4/5

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

Provides clear usage context: flags that the operation is mutating and not automatically reversible, and advises recording before-state with mureo_state_action_log_append for rollback. It also states the hard Meta prerequisites (privacy_policy_url and follow_up_action_url). However, it does not explicitly name alternatives or exclusion conditions (e.g., when to use lead_forms_duplicate instead), relying on the create verb and sibling naming to route the agent.

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