Skip to main content
Glama

meta_ads_creatives_create_dynamic

Create dynamic ads that let Meta automatically test and optimize combinations of images, headlines, and copy 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.
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.).
Behavior4/5

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

No annotations exist, so description carries full burden. It discloses mutability and suggests rolling back via 'mureo_state_action_log_append'. However, it lacks details on permissions, rate limits, or error handling, which would push to 5.

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?

Four sentences front-load the core purpose and usage, with zero wasted words. Each sentence adds distinct value.

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?

Given 9 parameters, no output schema, and no annotations, the description covers all critical aspects: what it does, when to use, prerequisites, rollback advice, and return value. It equips the agent to decide and invoke correctly.

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%, but description adds value by reinforcing constraints ('Supply 2–10 images, 1–5 of each text field') and providing placement advice ('~40 characters fits most placements'). Not essential but helpful.

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 'Creates a Dynamic Creative' with the specific verb and resource. It distinguishes from sibling tools by explicitly naming 'meta_ads_creatives_create' for static single-image ads and 'meta_ads_creatives_create_carousel' for multi-card layouts.

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?

Explicitly states when to use ('when you want Meta to learn the best-performing asset mix') and when not to (for static or carousel ads). Provides alternatives and prerequisites like uploading images first.

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