Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

meta_ads_creatives_create_lead

Create a Meta Lead Ad creative linked to an instant form for lead generation campaigns. Returns the new creative ID and object story 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
nameYesCreative name shown in Ads Manager. Internal label — not visible to end users.
reasonNoWhy this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.
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.
messageNoPrimary ad body text shown above the creative. Plain text, emoji allowed. ≤125 characters fits most placements without truncation.
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.
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.
link_urlYesFallback destination URL for placements where the in-app form cannot render. Must be HTTPS and domain-verified on the ad account.
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.
image_urlNoPublic HTTPS image URL. Auto-uploaded to image_hash. Mutually exclusive with image_hash.
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.
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.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.20.0
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Why this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.",
+  "maxLength": 500,
+  "type": "string"
+}
  2. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv0.9.17

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. It explicitly flags mutating behavior ('Mutating — not automatically reversible') and advises recording before-state with mureo_state_action_log_append. It also states the return fields. This is honest and covers the key behavioral concerns, though it doesn't address rate limits or auth specifics.

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 compact and front-loaded with the core purpose and return value. It then layers prerequisites, usage conditions, and a behavioral warning. Every sentence contributes actionable information, though it is slightly longer than necessary; a score of 4 reflects good structure without excess.

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?

For a tool with 13 parameters and no output schema, the description covers prerequisites, usage constraints, mutability, and return values. It explains video mode versus image mode and the fallback URL requirement. It doesn't mention error conditions or edge cases, but it provides enough for correct invocation in the common scenario. A 4 reflects that it's almost complete.

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 coverage is 100%, so the schema already documents every parameter in detail. The tool description adds only a small clarification about link_url being a fallback and the video mode behavior, which are also partially in the schema. It does not materially enhance understanding beyond the schema, so the baseline 3 is appropriate.

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 and resource: 'Creates a Lead Ad AdCreative attached to a Meta Instant Form.' It clearly differentiates from sibling tools like meta_ads_creatives_create and meta_ads_creatives_create_dynamic by specifying the Lead Ad + Instant Form combination, and it names the return values (id and object_story_id). This is unambiguous and distinct.

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 gives explicit usage context: 'Use under a campaign with objective=OUTCOME_LEADS and an ad set with optimization_goal=LEAD_GENERATION.' It also states the prerequisite that the lead form must exist and belong to the same Page, and clarifies link_url's role as a fallback. It doesn't explicitly name alternatives or exclusion cases, but the context is strong enough for an agent to decide when to invoke it.

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

Deploy Server

Other Tools