Skip to main content
Glama

meta_ads_products_update

Update one or more fields of an existing Meta Ads catalog product. Partial update — only supplied fields are changed, and rollback restores prior values.

Instructions

Updates one or more fields on an existing catalog product. Partial update — only supplied fields are changed. Returns the updated product. Mutating, reversible via rollback_apply (rollback restores prior field values). 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
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.
nameNoNew product display name.
descriptionNoNew product description.
availabilityNoNew inventory status. Meta suppresses 'out of stock' / 'discontinued' from DPA delivery.
priceNoNew price as 'amount ISO_CURRENCY' (e.g. '1200 JPY').
urlNoNew landing page URL (HTTPS).
image_urlNoNew primary image URL (HTTPS, publicly fetchable).
brandNoNew brand name.
categoryNoNew category path in Google Product Taxonomy format.
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that it performs a partial update (only supplied fields changed), is mutating, reversible via rollback_apply, and returns the updated product. It does not cover error conditions or authorization requirements, but the provided behavioral details are helpful.

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 concise: three sentences that efficiently convey purpose, behavior, and usage guidance. It is front-loaded with the core action and avoids unnecessary detail. Every sentence adds value.

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 has 10 optional parameters and no output schema, the description adequately covers key aspects: partial update semantics, mutability, reversibility, and differentiation from sibling tools. It lacks details on return format or error handling, but the coverage is sufficient for most use cases.

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 description coverage is 100%, so the input schema already documents each parameter comprehensively. The description adds no extra parameter-level meaning beyond stating it's a partial update. Baseline of 3 is appropriate as the schema does the heavy lifting.

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 partial update semantics. It specifies the verb 'Updates' and the resource 'existing catalog product', and distinguishes from full replacement via meta_ads.products.add. The mention of availability toggles further clarifies specific use cases.

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 provides when to use this tool (availability toggles) and when to use an alternative (meta_ads.products.add for full record replacement). It also mentions reversibility via rollback_apply, offering clear guidance on tool selection and consequences.

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