Skip to main content
Glama

delete_item

Delists a Xianyu listing by item ID, with optional force deletion when allowed and a dry-run mode to verify controls before acting.

Instructions

下架商品(默认)或在明确允许时删除商品

Args: item_id: 商品 ID force_delete: 当无法下架时是否尝试删除 dry_run: 是否仅检查按钮和确认弹窗,不真正执行

Returns: 处理结果

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": {
      "item_id": "<item_id>"
    },
    "name": "delete_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
item_idYes
force_deleteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the whole behavioral burden. It does disclose the important trait that the default path is non-destructive delisting and that deletion is conditional, plus that dry_run only verifies buttons/confirm dialogs, but it never says whether deletion is irreversible, what state the item is left in, or what permissions are required.

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?

Short and front-loaded: the core mode distinction is in the first line, followed by a compact Args/Returns block. The only waste is the trailing 'Returns: 处理结果', which conveys nothing the agent can act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter mutation tool with no annotations and no output schema, the description covers the mode distinction and every parameter, which is the essential core. It falls short on the return value ('处理结果' is vacuous) and on consequences/irreversibility of the delete path, which matter most for a destructive 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?

Schema description coverage is 0%, so the description is the only source of parameter meaning and it does explain all three: item_id as the商品 ID, force_delete as the fallback-to-delete switch, and dry_run as a check-only preview. The explanations are meaningful but thin on details such as the format of item_id or what dry_run returns when the check fails.

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?

Names a specific resource (商品) and two distinct operations with the default one marked ('下架商品(默认)'), so an agent knows immediately this is a delist-or-delete tool rather than an edit or publish tool. It does not explicitly contrast itself with edit_item or list_my_items, but the verb/resource pair is unambiguous.

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

Usage Guidelines4/5

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

States the default behavior (delist) and the condition under which the more drastic mode applies ('在明确允许时删除'), and force_delete is described as a fallback for when delisting fails. Missing explicit when-not guidance such as 'do not use for editing listing details' or preconditions about permissions, but the escalation logic is clear.

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