Skip to main content
Glama

meta_ads_creatives_create_carousel

Create a carousel ad with 2-10 swipeable cards, each with its own image or video, headline, and link. Returns the new creative ID.

Instructions

Creates a Carousel AdCreative with 2–10 swipeable cards. Returns the new creative id. Mutating, reversible via rollback_apply. Each card carries its own image (or video), name, description, and link — useful for product catalogs or multi-step narratives. For auto-optimized asset rotation use meta_ads_creatives_create_dynamic; for product-feed-driven carousels use meta_ads_creatives_create_collection.

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.
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.
cardsYesCarousel cards (2–10). Each card must have a link; image_hash, image_url, or video_id is required for the media.
linkYesMain destination URL — used for the See More card and as fallback when a card has no explicit link.
nameNoCreative name shown in Ads Manager. Optional.
Behavior4/5

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

Discloses mutation and reversibility, and that it returns the new creative ID. With no annotations, it carries the full burden; additional behaviors (e.g., media validation) are implied by schema but not expanded.

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-loaded with core action and purpose. No redundant information; every sentence adds value.

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?

Covers core function, return, reversibility, and sibling differentiation. Lacks mention of error handling or prerequisites beyond schema, but schema is comprehensive. Sufficient for a tool with moderate complexity and no output schema.

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 baseline is 3. Description adds context about card content (image/video, name, description, link) and return behavior, but does not significantly augment schema details.

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 tool creates a Carousel AdCreative with 2–10 swipeable cards, specifying the resource and cardinality. It distinguishes from siblings by naming alternatives for dynamic and collection carousels.

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 provides when-to-use guidance by contrasting with meta_ads_creatives_create_dynamic and meta_ads_creatives_create_collection. Also notes mutability and reversibility via rollback_apply, aiding decision-making.

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