Skip to main content
Glama

meta_ads_products_delete

Delete a single catalog product from Meta Ads permanently. Ads referencing the product will skip it on the next serve cycle. For temporary suppression, update availability to 'out of stock' instead.

Instructions

Deletes a single catalog product. Returns a success flag. Destructive — DPA / Collection ads that referenced this product_id will skip it on the next serve cycle. Reversible via rollback_apply (re-adds with the same retailer_id), but the Meta-assigned product_id changes on re-add, which can break hard-coded downstream references. For temporary suppression use meta_ads_products_update with availability='out of stock' instead.

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_idYesProduct ID to delete.
Behavior5/5

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

With no annotations, description fully discloses destructive nature, impact on DPA/Collection ads, reversibility via rollback_apply with product_id change, and consequences for downstream references. Leaves no behavioral surprises.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Sentences are purposeful and essential, but the description could be slightly shorter. Front-loaded with purpose. Consider combining the last two sentences for brevity.

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?

Given no output schema, no annotations, and 2 simple parameters, the description covers all critical information: purpose, effects, alternatives, and edge cases (product_id change on re-add). Completes the context for safe and correct usage.

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 covers both parameters (account_id, product_id) with descriptions. Description adds context about product_id reuse on re-add but does not add meaning beyond schema. Baseline 3 as schema coverage is 100%.

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?

Clearly states 'Deletes a single catalog product', a specific verb+resource. Distinguishes from update by mentioning alternative for temporary suppression.

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 advises against using for temporary suppression and recommends 'meta_ads_products_update with availability='out of stock'' as an alternative. Also explains when reversion is possible and its caveats.

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