Skip to main content
Glama

meta_ads_creatives_create_collection

Create a collection ad creative that pulls products from a catalog into a mobile-optimized storefront. Returns the new creative ID.

Instructions

Creates a Collection AdCreative that pulls products from a catalog into a mobile-optimized storefront layout. 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. Requires a Meta product catalog with the referenced product_ids — set up the catalog via meta_ads.catalogs.* tools first. For static card decks (non-catalog) use meta_ads_creatives_create_carousel instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkYesMain destination URL for the collection. HTTPS required.
nameNoCreative name shown in Ads Manager. Optional.
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.
product_idsYesProduct IDs drawn from the linked Meta catalog. List via meta_ads_products_list.
cover_video_idNoCover video ID shown above the product grid. Mutually exclusive with cover_image_hash.
cover_image_hashNoCover image hash shown above the product grid. Mutually exclusive with cover_video_id — supply one or neither.
Behavior5/5

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

Discloses mutating nature, irreversibility, and suggests before-state logging for rollback. Also notes return of creative id. With no annotations, the description fully covers behavioral traits.

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?

Concise at 5 sentences, front-loaded with core purpose, then critical behavioral info and sibling distinction. No wasted words.

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?

Covers purpose, usage guidance, behavioral transparency, prerequisites, and alternative tools. Adequate for an agent to decide and invoke correctly despite 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% with descriptions for all 7 parameters. The description adds no extra parameter semantics, so baseline 3 is appropriate.

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 Collection AdCreative from a catalog, distinguishing it from siblings like meta_ads_creatives_create_carousel. The verb 'Creates' and specific resource 'Collection AdCreative' provide precise purpose.

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 mentions when to use (catalog-based collection) and when not (static card decks, directing to sibling). Includes prerequisites: catalog setup via meta_ads.catalogs.* tools, and rollback recommendation via mureo_state_action_log_append.

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