Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

meta_ads_products_add

Adds one product to a Meta Product Catalog and returns its product_id; reuse a stable retailer_id to update the existing item instead of duplicating it.

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

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.
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.
approvalNoExternal approval this change carries out (recorded and shown, never verified)
categoryNoCategory path using Google Product Taxonomy format (e.g. 'Apparel & Accessories > Clothing > Tops'). Optional but strongly recommended for multi-category catalogs.
expectedNoExpected effects [{metric, direction, target?, horizon_days?, primary?}], exactly one primary:true when several; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold.
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.
decision_idNoA proposed decision this change carries out.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.33.0
    • changedInput schema / properties / expected / description
      Previous value: -"Expected effects [{metric, direction, target?, horizon_days?}]; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold."New value: +"Expected effects [{metric, direction, target?, horizon_days?, primary?}], exactly one primary:true when several; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold."
  2. Changed1 schema field changedv0.28.0
    • addedInput schema / properties / approval
      Added value: +{
+  "additionalProperties": false,
+  "description": "External approval this change carries out (recorded and shown, never verified)",
+  "properties": {
+    "approved_at": {
+      "maxLength": 64,
+      "type": "string"
+    },
+    "approved_by": {
+      "maxLength": 80,
+      "type": "string"
+    },
+    "reference": {
+      "maxLength": 128,
+      "type": "string"
+    }
+  },
+  "required": [
+    "reference",
+    "approved_by",
+    "approved_at"
+  ],
+  "type": "object"
+}
  3. Changed2 schema fields changedv0.26.0
    • addedInput schema / properties / decision_id
      Added value: +{
+  "description": "A proposed decision this change carries out.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / expected
      Added value: +{
+  "description": "Expected effects [{metric, direction, target?, horizon_days?}]; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold.",
+  "maxItems": 12,
+  "type": "array"
+}
  4. 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"
+}
  5. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  6. Changed1 schema field changedv1.0.7
    • changedInput schema / required
      Previous value: -[
-  "account_id",
-  "catalog_id",
-  "retailer_id",
-  "name",
-  "availability",
-  "condition",
-  "price",
-  "url",
-  "image_url"
-]New value: +[
+  "catalog_id",
+  "retailer_id",
+  "name",
+  "availability",
+  "condition",
+  "price",
+  "url",
+  "image_url"
+]
  7. Addedv0.9.12
  8. Removedv0.9.6
  9. Addedv0.9.2
  10. Removedv0.9.1
  11. 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, the description carries the full burden and does so: declares the operation mutating and 'not automatically reversible', describes the required before-state logging path, discloses rate-limit behavior, and explains the upsert-by-retailer_id side effect that surprises callers. This is substantially more than the schema or annotations provide.

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?

Four sentences, each earning its place: purpose+return first, then mutability/rollback, then bulk alternative, then upsert semantics. No filler and the critical constraints are front-loaded.

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 16-parameter mutation with a nested approval object and no output schema, the description covers the return value, mutability, rollback path, rate limits, and the upsert nuance. Combined with 100% schema coverage, an agent has everything needed to call 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 coverage is 100%, so every parameter, enum, and nested approval object is already documented in the schema. The description's retailer_id/upsert note largely restates the schema's own 'Used as the upsert key' text, so it adds only marginal value beyond structured fields; baseline 3 applies.

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?

Opens with a specific verb and resource ('Adds a single product to a Meta Product Catalog') and states the return value ('Returns the new product_id'). It distinguishes itself from siblings by pointing to meta_ads_feeds_create for bulk ingestion and from meta_ads_products_update via the retailer_id upsert note.

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?

Gives explicit when-to-use and when-not: single add vs 'bulk ingestion prefer a scheduled feed (meta_ads_feeds_create)', with the rationale that Meta rate-limits single-product adds aggressively. It also warns against rollback risk by naming mureo_state_action_log_append as the mitigation.

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