Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

meta_ads_creatives_create_dynamic

Create dynamic ads by letting Meta automatically combine and test your images, headlines, and CTAs to find the best-performing mix.

Instructions

Creates a Dynamic Creative — Meta auto-generates and optimises combinations from multiple images, headlines, bodies, and CTAs. Returns the new creative id. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. Use when you want Meta to learn the best-performing asset mix rather than testing manually. For static single-image ads use meta_ads_creatives_create; for explicitly-controlled multi-card layouts use meta_ads_creatives_create_carousel. Supply 2–10 images, 1–5 of each text field; Meta combines them at serve time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCreative name shown in Ads Manager.
bodiesYesPrimary body text variants. 1–5 accepted. Meta recommends ≤125 characters per body.
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.
titlesYesHeadline variants. 1–5 accepted. ~40 characters fits most placements.
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.
link_urlYesDestination URL shared across all combinations. Must be HTTPS and domain-verified.
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.
descriptionsNoOptional link-caption variants (0–5). Not all placements render these.
image_hashesYesImage hashes to include in the rotation. 2–10 recommended for meaningful optimization; Meta accepts up to 10. Upload via meta_ads_creatives_upload_image / meta_ads_images_upload_file first.
call_to_actionsNoOptional CTA variants (0–5). Values drawn from the same set as meta_ads_creatives_create (LEARN_MORE / SIGN_UP / SHOP_NOW / etc.).

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. Changed1 schema field changedv1.0.7
    • changedInput schema / required
      Previous value: -[
-  "account_id",
-  "name",
-  "page_id",
-  "image_hashes",
-  "bodies",
-  "titles",
-  "link_url"
-]New value: +[
+  "name",
+  "page_id",
+  "image_hashes",
+  "bodies",
+  "titles",
+  "link_url"
+]
  4. Addedv0.9.12
  5. Removedv0.9.6
  6. Addedv0.9.2
  7. Removedv0.9.1
  8. Addedv1.0.5

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are present, so the description carries the full behavioral disclosure burden. It clearly states the operation is mutating and not automatically reversible, recommends recording before-state via mureo_state_action_log_append for rollback, mentions the return value, and explains that Meta combines assets at serve time.

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?

The description is dense but well-structured: definition, side effect/rollback, usage trigger, sibling routing, and asset-count constraints. Every sentence earns its place and the most identifying information is front-loaded.

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?

For a mutating 10-parameter tool with no annotations and no output schema, the description covers the outcome, return value, safety considerations, prerequisite behavior, and sibling alternatives. The 100%-coverage schema handles parameter-level details, so nothing critical is left for the agent to guess.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds useful cross-parameter guidance beyond the schema: supply 2–10 images and 1–5 of each text field for meaningful optimization, and clarifies that Meta combines them at serve time.

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 opens with a specific verb and resource: 'Creates a Dynamic Creative'. It then explains the defining behavior — Meta auto-generates and optimises combinations from multiple assets — and names the closest sibling tools, so an agent can distinguish it without opening schemas.

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?

The description gives explicit selection criteria: use this tool when Meta should learn the best-performing asset mix rather than manual testing. It also names alternatives with concrete conditions: static single-image ads should use meta_ads_creatives_create, and explicitly-controlled multi-card layouts should use meta_ads_creatives_create_carousel.

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