Publish a second-hand item to Goofish by providing title, description, and price. Optionally add category and images to enhance the listing.
Publish a new Goofish/Xianyu second-hand item listing.
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | 商品标题 | |
| desc | Yes | 商品描述 | |
| price_yuan | Yes | 售价（元），如 99.5 | |
| category_id | No | 分类ID（可选） | |
| images | No | 图片本地路径列表（如 /tmp/img.jpg），可选 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description merely states 'Publish' without disclosing behavioral traits like authentication needs, side effects, or whether the operation is reversible.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence with no unnecessary words, efficiently conveying the tool's purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 5 parameters and no output schema, the description lacks essential details such as return values, error handling, or behavior on success/failure, and does not differentiate from sibling tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3; the description adds no additional meaning beyond the schema’s basic parameter descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Publish' and the resource 'Goofish/Xianyu second-hand item listing', distinguishing it from sibling tools like get_item_detail, monitor_keyword, and search_items.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage guidelines are provided; the description does not explain when to use this tool, prerequisites, or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mercy719/goofish-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server