Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

meta_ads_catalogs_create

Create a new Meta Product Catalog under a Business ID and receive its catalog_id. Establishes the container needed before adding products individually or scheduling bulk feed imports.

Instructions

Creates a new Product Catalog under a Meta Business. Returns the new catalog_id. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. Catalogs are the container — add products individually via meta_ads_products_add, or schedule bulk imports via meta_ads_feeds_create.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCatalog name shown in Commerce Manager. Must be unique within the Business.
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.
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.
business_idYesMeta Business ID that will own the new catalog.

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.5/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 of behavioral disclosure, and it does so well. It explicitly labels the operation as mutating, warns that it is not automatically reversible, and recommends a compensating action using mureo_state_action_log_append. It also states the return contract by mentioning the new catalog_id. This exceeds typical transparency for a create tool.

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?

Three sentences deliver the purpose, return value, mutation warning, rollback path, and downstream alternatives with no filler. The most essential facts are front-loaded, and every sentence earns its place. The structure is tight and scannable.

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 simple create operation with no output schema and no annotations, the description is complete. It covers what the tool does, what it returns, its mutability and irreversibility, how to mitigate rollback risk, and how it relates to the surrounding catalog workflow. Nothing essential is missing for an agent to invoke it correctly.

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 four parameters. The description does not add extra meaning beyond the schema's parameter details. Baseline 3 is appropriate because the description is not required to compensate for any schema gaps.

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 identifies the exact action ('Creates a new Product Catalog under a Meta Business') and the return value ('Returns the new catalog_id'). It is clearly distinct from sibling catalog operations by the verb 'creates', and it also situates this tool relative to downstream product/feed tools. No ambiguity remains about what resource is being acted upon.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives practical routing guidance: after catalog creation, products should be added via meta_ads_products_add or bulk-imported via meta_ads_feeds_create. This clarifies when this tool is the right choice versus the related product/feed tools. It does not explicitly state conditions like 'when no existing catalog should be reused', but the context is sufficiently clear.

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