Skip to main content
Glama

meta_ads_creatives_create_lead

Creates a Lead Ad creative for a Meta Instant Form. Requires an existing form, page, and HTTPS fallback URL. Returns the new creative's ID.

Instructions

Creates a Lead Ad AdCreative attached to a Meta Instant Form. Returns the new creative's id and object_story_id. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. Use under a campaign with objective=OUTCOME_LEADS and an ad set with optimization_goal=LEAD_GENERATION. Pre-requisite: the lead form must exist (create via meta_ads_lead_forms_create) and belong to the same Facebook Page. link_url is the fallback landing page for placements where the in-app form cannot render; it must be HTTPS and domain-verified on the ad account.

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.
nameYesCreative name shown in Ads Manager. Internal label — not visible to end users.
page_idYesFacebook Page ID that the ad will be published as. Must be a page the authenticated user has permission to post from. Required by Meta for every creative — ads cannot run without a page identity.
form_idYesLead Form ID returned by meta_ads_lead_forms_create or listed via meta_ads_lead_forms_list. The form must belong to the supplied page_id.
link_urlYesFallback destination URL for placements where the in-app form cannot render. Must be HTTPS and domain-verified on the ad account.
image_urlNoPublic HTTPS image URL. Auto-uploaded to image_hash. Mutually exclusive with image_hash.
image_hashNoPre-uploaded image hash from meta_ads_creatives_upload_image / meta_ads_images_upload_file. Mutually exclusive with image_url. In video mode (when video_id is set), used as the video thumbnail.
video_idNoPre-uploaded video ID from meta_ads_videos_upload / meta_ads_videos_upload_file. When supplied, the creative becomes a video Lead Ad — object_story_spec.video_data is used (not link_data) and lead_gen_form_id is nested under call_to_action.value. image_url is rejected in video mode; supply image_hash directly as the thumbnail.
messageNoPrimary ad body text shown above the creative. Plain text, emoji allowed. ≤125 characters fits most placements without truncation.
headlineNoHeadline shown with the creative. ~40 characters fits most placements. Mapped to link_data.name in image mode and video_data.title in video mode.
descriptionNoLink-caption text shown below the headline. Optional; not all placements render it.
call_to_actionNoCTA button label. SIGN_UP is the canonical Lead Ad CTA and the default. Choose the one that matches the form's purpose.
Behavior5/5

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

With no annotations provided, the description fully discloses the mutating nature and irreversibility, advising to record before-state for rollback. It also details behavioral nuances like image_url/video_id mutual exclusivity and fallback link requirements. This covers key behavioral traits beyond what annotations would typically provide.

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?

The description is one coherent paragraph that front-loads the core purpose and return values. It is concise given the complexity of the tool but could be slightly restructured for readability. Every sentence adds value, with no unnecessary filler.

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 12 parameters and no output schema or annotations, the description covers purpose, usage context, behavioral notes, and parameter interplay. It mentions the return values and prerequisites. While it could include more details on error conditions or rate limits, it is largely complete for an experienced Meta Ads user.

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?

The description adds significant value beyond the input schema, which already has 100% coverage. It explains parameter interactions (e.g., image_url and image_hash mutual exclusivity, video mode changes), fallback behavior of link_url, and the purpose of each field in context. This helps the agent understand parameter relationships and constraints.

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 the specific verb and resource: 'Creates a Lead Ad AdCreative attached to a Meta Instant Form.' It also specifies the return values (id and object_story_id). The tool is well-differentiated from sibling tools like meta_ads_creatives_create (general) and meta_ads_creatives_create_carousel by its focus on Lead Ads.

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?

The description explicitly states the required campaign and ad set conditions (objective=OUTCOME_LEADS, optimization_goal=LEAD_GENERATION). It also mentions the prerequisite lead form and page ownership. While it does not explicitly exclude other creative creation tools, it provides sufficient context for correct usage.

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