Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

meta_ads_products_delete

Permanently delete a single product from your Meta Ads catalog. Ads referencing it will skip it on the next serve, so this action is irreversible.

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. Not automatically reversible — record before-state with mureo_state_action_log_append if you may need to roll back (and note that re-adding with the same retailer_id assigns a new Meta product_id, 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
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.
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.

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?

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It discloses destructiveness, the effect on DPA/Collection ads, irreversibility, the consequence of re-adding with the same retailer_id, and the expected return of a success flag. This is exceptionally transparent for a mutation tool.

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 compact yet dense, with the main purpose front-loaded, followed by consequences, irreversibility, rollback guidance, and an alternative. Every sentence adds essential value; there is no redundancy or filler.

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 destructive action, this description covers all essential aspects: what it does, side effects on ads, irreversibility, rollback strategy, alternative approach, and the return value. There is no output schema, but the success flag is mentioned. Nothing an agent needs to invoke this safely and correctly 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 description coverage is 100%, so the baseline is 3. The description adds important context about the product_id parameter (re-adding assigns a new Meta product_id, breaking hard-coded references) and the rollback recommendation, which goes beyond what the schema states. It enhances understanding of the parameter's behavioral implications, justifying a 4.

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?

States a specific verb and resource ('Deletes a single catalog product') and clearly differentiates from the update sibling by name and purpose. An agent can immediately understand what this tool does and how it differs from meta_ads_products_update.

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 provides a conditional alternative ('For temporary suppression use meta_ads_products_update with availability='out of stock' instead') and gives rollback guidance via mureo_state_action_log_append. This gives clear when-to-use and when-not-to-use instructions, including how to avoid the destructive action when a non-destructive option exists.

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