Skip to main content
Glama
Sign In
meta-ads-mcp

meta-ads-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_dynamic_creative

Create a dynamic creative using asset_feed_spec so Meta automatically combines images, videos, titles, bodies, and CTAs to find the best performing ad combinations.

Instructions

Create a dynamic creative with asset_feed_spec. Meta automatically combines different images, videos, titles, bodies, and CTAs to find the best performing combinations.

Input Schema

NameRequiredDescriptionDefault
nameYesCreative name
account_idNoAd account ID to create the creative in (e.g. 'act_123' or '123'). Falls back to META_AD_ACCOUNT_ID env var if omitted.
asset_feed_specYesJSON string of asset_feed_spec with arrays: images (hash), videos (video_id), bodies (text), titles (text), descriptions (text), call_to_action_types
destination_specNoJSON object controlling the destination; set destination_type=WEBSITE_AND_SHOP_OPT_OUT to opt out of the v26 Shops default
object_story_specNoJSON object containing the associated page_id and optional instagram_user_id
degrees_of_freedom_specNoJSON object for Advantage+ creative controls, including creative_features_spec.image_animation, video_filtering, and video_uncrop
wamo_whatsapp_identity_specNoJSON object with wamo_whatsapp_identity_id or whatsapp_phone_number for WhatsApp Status ads; sent at the creative's top level

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.6.1
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Ad account ID to create the creative in (e.g. 'act_123' or '123'). Falls back to META_AD_ACCOUNT_ID env var if omitted.",
+  "type": "string"
+}
    • addedInput schema / properties / degrees_of_freedom_spec
      Added value: +{
+  "description": "JSON object for Advantage+ creative controls, including creative_features_spec.image_animation, video_filtering, and video_uncrop",
+  "type": "string"
+}
    • addedInput schema / properties / destination_spec
      Added value: +{
+  "description": "JSON object controlling the destination; set destination_type=WEBSITE_AND_SHOP_OPT_OUT to opt out of the v26 Shops default",
+  "type": "string"
+}
    • addedInput schema / properties / object_story_spec
      Added value: +{
+  "description": "JSON object containing the associated page_id and optional instagram_user_id",
+  "type": "string"
+}
    • addedInput schema / properties / wamo_whatsapp_identity_spec
      Added value: +{
+  "description": "JSON object with wamo_whatsapp_identity_id or whatsapp_phone_number for WhatsApp Status ads; sent at the creative's top level",
+  "type": "string"
+}
  2. First observedv1.2.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations, so the description carries the burden. It discloses the useful behavioral trait that Meta automatically combines assets, but omits permissions/auth needs, the account_id env-var fallback, validation behavior, and what a successful call yields.

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?

Two tight sentences with the purpose front-loaded and the mechanism following; zero filler.

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

Completeness3/5

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

For a 7-parameter creation tool with no annotations and no output schema, the description should say more about the optional specs (destination_spec, degrees_of_freedom_spec, wamo_whatsapp_identity_spec) and the return value. The rich schema partially compensates.

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 itself documents all seven parameters. The description's mention of images, videos, titles, bodies and CTAs largely restates the asset_feed_spec schema description, adding little new semantics.

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

Purpose4/5

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

States a specific verb and resource ('Create a dynamic creative') and explains the distinguishing mechanism (Meta auto-combines assets). This separates it from the generic sibling create_creative, though it never names that sibling explicitly.

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?

Usage is only implied by the 'dynamic creative' framing; there is no explicit when-to-use-this-vs-create_creative guidance, no prerequisites, and no mention of what happens if asset_feed_spec is incomplete.

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