Skip to main content
Glama

meta_ads_products_add

Add a single product to a Meta Product Catalog using a stable retailer_id as the upsert key. Returns the new product_id. For bulk ingestion, use a scheduled feed instead.

Instructions

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

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

Since no annotations are provided, the description carries full burden. It discloses mutability, reversibility via rollback_apply, rate limit context, and upsert behavior. However, it does not detail required permissions or error handling, which would elevate transparency further.

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 a single dense paragraph that front-loads the core purpose and return value. Every sentence adds value (return value, reversibility, bulk alternative, rate limit, upsert key). No wasted words.

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 no output schema, the description covers return value and key caveats like rate limits and upsert behavior. It could mention failure modes or prerequisites, but it is sufficiently complete for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameters are well-documented. The description adds context for retailer_id (upsert key), price format example, and image_url size recommendation, going beyond the schema. This adds meaningful value.

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 action ('Adds a single product'), the target resource ('Meta Product Catalog'), and the return value ('Returns the new product_id'). It distinguishes itself from bulk ingestion via mention of 'meta_ads_feeds_create', making its scope specific.

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?

Provides explicit guidance: 'For bulk ingestion prefer a scheduled feed (meta_ads_feeds_create) — Meta rate-limits single-product adds aggressively.' Also explains the upsert behavior with retailer_id, helping the agent decide when to use this tool.

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