Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

meta_ads_creatives_create_collection

Create a Collection ad creative that pulls products from a Meta catalog into a mobile-optimized storefront layout and returns the new creative ID. Ideal for building shoppable product-grid ads.

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.
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.
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.

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. Addedv0.9.12
  4. Removedv0.9.6
  5. Addedv0.9.2
  6. Removedv0.9.1
  7. Addedv1.0.5

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does an excellent job: it discloses that the operation is mutating, not automatically reversible, and suggests recording before-state via mureo_state_action_log_append for rollback. It also reveals the return value (new creative id) and a prerequisite.

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 tightly structured and front-loaded: purpose, return value, mutation warning, prerequisite, and alternative are each covered in a short sentence with no filler. Every sentence earns its place.

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 tool with no annotations and no output schema, this is unusually complete: it covers what the operation does, what it returns, the rollback caveat, the catalog prerequisite, and the relevant alternative tool. An agent has enough to decide whether to call it and how to call it safely.

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 description coverage is 100%, so the schema already documents all 8 parameters in detail. The description adds useful context about product catalog prerequisites, but it does not add substantial per-parameter meaning beyond what the schema already provides.

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 states the exact verb and resource: it creates a Collection AdCreative that pulls products from a catalog into a mobile-optimized storefront, and explicitly says it returns the new creative id. This sets it apart from the many sibling creative tools, especially by naming the carousel alternative.

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?

It gives an explicit when-to-use condition: a Meta product catalog with the referenced product_ids must exist, and it points to catalog setup tools. It also gives a clear when-not-to-use rule by directing non-catalog static card decks to 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