Skip to main content
Glama
Sign In
FishClaw MCP

FishClaw MCP

by TnoobT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

manage_item

Destructive

Delist items to draft or delete them permanently on Xianyu. Use after obtaining item URL from get_selling_items.

Instructions

对指定商品执行下架或删除操作，内部自动跳转商品详情页并处理确认弹窗。 ⚠️ delete 操作永久删除商品，不可恢复。 请先调用 get_selling_items 获取商品链接，再传入此工具。

Args: item_url: 商品详情页 URL（从 get_selling_items 结果中获取）。 action: delist=下架（转为草稿，可重新上架）；delete=永久删除。

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_url": "<item_url>",
      "action": "<action>"
    },
    "name": "manage_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_urlYes
actionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

The description adds context beyond the destructiveHint annotation: it notes that delete is irreversible while delist is reversible (turns to draft). There is no contradiction with annotations.

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?

The description is clear but slightly verbose with emoji and two languages. The Args section is well-structured, and every sentence adds value, though it could be more concise.

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?

Given the tool's simplicity (two required params, output schema exists), the description covers prerequisites, action effects, and internal behavior. It is complete for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage, the description explains that item_url comes from get_selling_items and defines each action enum value. This adds critical meaning beyond the raw schema.

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 clearly states that the tool delists or deletes items, specifying the two actions and their effects. It distinguishes itself from sibling tools like draft_item and publish_item by focusing on removal operations.

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?

It explicitly instructs to call get_selling_items first to obtain the item_url, explains when to use delist vs delete, and warns that delete is permanent. This provides clear when-to-use guidance.

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