Skip to main content
Glama

Delete Product

sirv_delete_product
DestructiveIdempotent

Permanently delete a single product from the Studio catalogue by its id. This action cannot be undone, so confirm with the user first; linked library assets remain in the library.

Instructions

Delete one product from the Studio catalogue. Products have no trash, so this cannot be undone: ask the user first.

The library assets linked to it stay in the library. To delete up to 25 products in one call, use sirv_bulk_edit_products.

Returns the product id.

Credits: free.

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": {
      "id": "<id>"
    },
    "name": "sirv_delete_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the product to delete for good, from sirv_list_products
orgIdNoWorkspace id from sirv_list_organizations. Default: the workspace you signed in to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • changedInput schema / properties / id / description
      Previous value: -"Product ID to delete"New value: +"Id of the product to delete for good, from sirv_list_products"
    • changedInput schema / properties / orgId / description
      Previous value: -"Organization ID (uses default org if omitted)"New value: +"Workspace id from sirv_list_organizations. Default: the workspace you signed in to"
    • addedInput schema / properties / orgId / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds context annotations cannot carry: there is no trash, the deletion is irreversible, linked library assets survive, the return value is the product id, and the call is free of credits.

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 short sentences, each earning its place: action, irreversibility warning, asset side effect, bulk alternative, return value, cost. The destructive warning is front-loaded where it matters most.

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 two-parameter destructive tool with no output schema, the description covers safety, side effects, alternative routing, return value, and cost — nothing an agent needs to call it correctly is missing.

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%, with both id and orgId documented including their source tools and the orgId default. The description adds no parameter-level detail beyond the schema, so the 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?

States a specific verb and resource ('Delete one product from the Studio catalogue') and immediately scopes it against the sibling bulk tool, so an agent can distinguish it from sirv_bulk_edit_products without opening either schema.

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?

Gives explicit when-to-use routing ('To delete up to 25 products in one call, use sirv_bulk_edit_products') plus a mandatory precondition ('ask the user first'), which is exactly the guidance needed for a destructive single-item operation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.