Skip to main content
Glama

meta_ads_products_add

Adds a product to a Meta Product Catalog. Uses retailer_id as key to update existing products; rate-limited, use for single additions, not bulk.

Instructions

Adds a single product to a Meta Product Catalog. Returns the new product_id. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. For bulk ingestion prefer a scheduled feed (meta_ads_feeds_create) — Meta rate-limits single-product adds aggressively. Meta requires a stable retailer_id per product; adding a second product with the same retailer_id updates the existing record rather than creating a duplicate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesProduct landing page URL. Must be HTTPS and reachable — Meta periodically probes URLs and marks broken ones.
nameYesProduct display name shown in DPA / Collection ads.
brandNoBrand name. Optional but improves match quality for broad-intent DPA shoppers.
priceYesPrice as a string with currency code, e.g. '1000 JPY', '9.99 USD'. Meta parses the string into amount + ISO currency. Must match the catalog's supported currencies.
categoryNoCategory path using Google Product Taxonomy format (e.g. 'Apparel & Accessories > Clothing > Tops'). Optional but strongly recommended for multi-category catalogs.
conditionYesProduct condition. Required by Meta for catalog eligibility in most verticals.
image_urlYesPrimary product image URL. HTTPS, publicly fetchable. Meta recommends at least 500×500px.
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.
catalog_idYesCatalog to add the product into.
descriptionNoProduct description. Shown on some placements and surfaces; Meta also uses it as a weak targeting signal.
retailer_idYesAdvertiser's stable SKU / product identifier. Used as the upsert key — a second add with the same retailer_id updates the existing product.
availabilityYesInventory status. Meta suppresses 'out of stock' and 'discontinued' items from DPA delivery.
Behavior4/5

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

The description discloses mutability, irreversibility, and the need for manual rollback preparation, which is essential since no annotations are provided. It also explains the upsert behavior and rate limits. A minor gap: no mention of error handling or idempotency, but overall strong.

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 five sentences, front-loading the main action and return. It efficiently covers mutation, alternatives, rate limits, and key parameter behavior without repetition or fluff.

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?

Given the tool's complexity (12 params, no output schema), the description covers the return value, mutation semantics, rollback advice, and important constraints. It lacks explicit error handling discussion but is otherwise sufficiently complete for a single-product add tool.

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?

With 100% schema coverage, the baseline is 3. The description adds some cross-cutting context (upsert key, rate limits, rollback) but does not provide new per-parameter details beyond what the schema already describes. Value-add is moderate.

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 starts with a specific verb ('Adds') and resource ('single product to a Meta Product Catalog'), clearly stating the tool's action and return value. It distinguishes from sibling tools like meta_ads_feeds_create for bulk ingestion, avoiding ambiguity.

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?

The description explicitly notes when to avoid this tool ('For bulk ingestion prefer a scheduled feed') due to aggressive rate limiting, and advises recording before-state for rollback. This provides clear usage context and alternatives.

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