Skip to main content
Glama

meta_ads_creatives_create_carousel

Create a carousel ad with 2–10 swipeable cards, each with its own image, name, description, and link. Returns the new creative ID.

Instructions

Creates a Carousel AdCreative with 2–10 swipeable cards. 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. 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
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.
cardsYesCarousel cards (2–10). Each card must have a link; image_hash, image_url, or video_id is required for the media.
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.
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.
Behavior4/5

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

Describes the operation as mutating and not automatically reversible, suggesting a rollback strategy. Without annotations, this is good but lacks details on permissions, rate limits, or error behavior. However, the core behavioral trait (mutation requiring rollback consideration) is covered.

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 concise sentences with no fluff. Front-loaded with purpose, then return value, behavioral note, card explanation, and alternatives—all in a logical order.

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 the 100% schema coverage, no output schema, and presence of sibling tools, the description is complete. It covers what the tool does, how to use it, when to use alternatives, and the mutating nature.

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. The description adds context about cards having their own media and links and the tool's use cases, but doesn't provide additional per-parameter meaning beyond the schema.

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 specifies the exact action: creating a Carousel AdCreative with 2–10 swipeable cards, returning the creative id. It clearly distinguishes from sibling tools like meta_ads_creatives_create_dynamic and meta_ads_creatives_create_collection by naming their use cases.

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 (product catalogs, multi-step narratives) and provides alternatives for auto-optimized assets or product-feed-driven carousels. Also advises recording before-state for rollback, indicating a safety measure.

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