Skip to main content
Glama

delete_listing

Destructive

Delete a listing (SKU) from the seller catalog on Amazon. ACTION, destructive: show the SKU and get explicit user approval first. Returns the Amazon submission status.

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": {
      "sku": "<sku>"
    },
    "name": "delete_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuYesSKU del venditore, esattamente come in Seller Central (maiuscole e minuscole contano).
account_idNoID dell'outpost Amazon (= un seller su uno specifico marketplace; vedi list_clients). Opzionale se il token è legato a un solo outpost.
confirm_idNoToken di conferma ritornato dall'anteprima. Ripassa lo STESSO payload + confirm_id per eseguire davvero la scrittura.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / sku / description
      Added value: +"SKU del venditore, esattamente come in Seller Central (maiuscole e minuscole contano)."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered structurally; the description adds the human-approval requirement and the return value (submission status). It does not say whether deletion is reversible, what happens to the Amazon-side catalog entry, or that a preview/confirm_id step is required before the write executes.

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?

Three short sentences, front-loaded with the action and immediately followed by the safety gate. Every sentence carries weight, with only the phrase "ACTION," being mildly redundant against the destructive annotation.

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 destructive single-item mutation with full annotations and full schema coverage, the definition covers what it does, the approval gate and the return value. The remaining gap is routing versus bulk_delete_listings and the two-step confirm flow, the latter being recoverable from the schema.

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 schema already explains sku case-sensitivity, account_id scoping and the confirm_id token. The description adds no parameter-level meaning beyond naming the SKU, hitting the baseline for full coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Delete a listing (SKU) from the seller catalog on Amazon") with clear scope. It does not distinguish itself from the sibling bulk_delete_listings, leaving the agent to infer the single-vs-bulk split from names alone.

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

Usage Guidelines3/5

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

Provides a clear pre-call gate ("show the SKU and get explicit user approval first"), which is genuine when-to-use guidance for a destructive action. It never names an alternative such as bulk_delete_listings, and it omits the preview-then-confirm sequence implied by the confirm_id parameter.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources