Skip to main content
Glama

meta_ads_products_update

Partially updates one or more fields on an existing Meta Ads catalog product, such as price or availability. 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').
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.
Behavior5/5

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

No annotations provided, so description carries full burden. It discloses mutation, irreversibility, and suggests recording before-state with mureo_state_action_log_append.

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 concise sentences, each adding distinct value: purpose, update behavior, reversibility warning, and usage distinction. No redundancy.

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 10 parameters, no output schema, and no annotations, the description covers purpose, usage, and behavioral warnings adequately. Lacks error handling but sufficient for selection and invocation.

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% with descriptions for all 10 parameters. Description adds context of partial update but no additional parameter-specific details beyond schema.

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 it updates an existing catalog product with a partial update, distinguishing from full replacement via the add tool.

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 (availability toggles) and when not to (full replacement), naming the alternative tool meta_ads.products.add.

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