Skip to main content
Glama
Sign In
Meta MCP Server

Meta MCP Server

by oliverames
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete Product

meta_delete_product
Destructive

Permanently delete a product from your catalog using its ID. This action cannot be undone.

Instructions

Deletes a product from a catalog.

Args:

  • product_id (string): The product ID

This action is permanent and cannot be undone.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product_id": "<product_id>"
    },
    "name": "meta_delete_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYesProduct ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.2

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false. The description adds 'This action is permanent and cannot be undone,' reinforcing the destructive hint with irreversibility. This provides additional behavioral context beyond the annotations.

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 highly concise: one sentence for the action, a simple Args block, and a one-sentence permanence warning. It is front-loaded and contains no unnecessary wording.

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?

For a simple delete operation with one parameter, the description covers the action, input, and permanence, and the annotations cover the safety profile. It does not elaborate on cascading effects or return values, but these are not critical for such a simple tool.

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?

The schema describes product_id as a required string 'Product ID' with 100% coverage. The description repeats this information without adding extra meaning such as format, source, or validation rules. Since schema coverage is high, baseline 3 applies.

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 states 'Deletes a product from a catalog' with a specific verb and resource. It is clearly distinct from sibling tools like meta_get_product, meta_create_product, and meta_update_product by naming the delete operation and the target resource.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that meta_update_product should be used for modifications, nor does it give any contextual conditions or exclusions.

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