Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

meta_ads_products_update

Update specific fields on an existing Meta Ads catalog product, including availability, price, name, or URL. Returns the updated product.

Instructions

Updates one or more fields on an existing catalog product. Partial update — only supplied fields are changed. Returns the updated product. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. For availability toggles (in stock ↔ out of stock) this is the correct entry point; for full record replacement call meta_ads.products.add with the same retailer_id (the add is upsert-semantic).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoNew landing page URL (HTTPS).
nameNoNew product display name.
brandNoNew brand name.
priceNoNew price as 'amount ISO_CURRENCY' (e.g. '1200 JPY').
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.
categoryNoNew category path in Google Product Taxonomy format.
image_urlNoNew primary image URL (HTTPS, publicly fetchable).
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_idYesMeta-assigned product_id to update.
descriptionNoNew product description.
availabilityNoNew inventory status. Meta suppresses 'out of stock' / 'discontinued' from DPA delivery.

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.9/5.0
Behavior5/5

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

With no annotations present, the description carries the full burden and meets it: it discloses that the operation is mutating, not automatically reversible, advises a rollback mitigation via mureo_state_action_log_append, and states the return value ('Returns the updated product'). This is far beyond minimal disclosure.

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?

Five sentences, each earning its place: purpose, partial-update semantics, return value, mutation warning with mitigation, and alternative tool routing. Information is front-loaded and there is no redundant or promotional language.

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 an 11-parameter mutation tool with 100% schema coverage and no output schema, the description covers the operation's scope, behavior, side effects, and alternatives. It even names the rollback companion tool. Nothing needed for correct invocation or selection is missing.

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 the baseline is 3. The description adds meaningful aggregate semantics—'Partial update — only supplied fields are changed'—which clarifies that omitted fields are preserved, a fact not directly inferable from individual optional parameter descriptions. This boosts it above baseline, though it doesn't add per-parameter details.

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 opens with a specific verb and resource ('Updates one or more fields on an existing catalog product') and immediately clarifies the partial-update scope, distinguishing it from full-replacement tools. The later reference to meta_ads.products.add as the full-replacement alternative reinforces sibling differentiation.

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?

Explicitly states when to use this tool ('For availability toggles ... this is the correct entry point') and when not to, naming the alternative ('for full record replacement call meta_ads.products.add'). This gives the agent clear routing criteria against sibling tools.

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