Skip to main content
Glama

publish_item

Publish a secondhand listing to Xianyu with title, description, price, images and optional category, condition, location and delivery. Use dry_run to validate the form before submitting.

Instructions

发布闲鱼商品

Args: title: 标题(最多 20 字) description: 描述(最多 1000 字) price: 价格 images: 图片路径列表 category: 分类 location: 地区 condition: 新旧程度 delivery: 配送方式 dry_run: 是否仅预检查表单,不真正提交发布

Returns: 发布结果 {"success": bool, "item_id": str, "message": str}

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": {
      "title": "<title>",
      "description": "<description>",
      "price": "<price>",
      "images": "<images>"
    },
    "name": "publish_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceYes
titleYes
imagesYes
dry_runNo
categoryNo
deliveryNo包邮
locationNo
conditionNo全新
descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose two genuinely useful behavioral facts beyond the schema: dry_run performs a form pre-check without submitting, and the return payload shape is success/item_id/message. It says nothing about authentication requirements, rate limits, or whether a failed publish leaves partial state, which matters for a mutation tool.

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 purpose line is front-loaded in a single sentence, followed by a compact parameter list and a short Returns block. Restating each English parameter name is mild redundancy, but it is the vehicle for the added semantics and stays short overall.

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

Completeness2/5

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

For a 9-parameter, 4-required mutation tool with zero annotation coverage and no output schema, the definition is thin. It compensates partially by documenting the return payload inline, but it omits the caller's preconditions, failure behavior, and any routing guidance against edit_item or list_my_items — the things an agent most needs before publishing a real listing.

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

Parameters4/5

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

Schema description coverage is 0% — parameters have only bare titles — so the Args block is doing real work: it supplies length limits (title ≤20 chars, description ≤1000 chars) and clarifies that images is a list of file paths. Several entries (category/location/condition/delivery) are near-tautological translations of the parameter names and give no accepted value sets, so it falls short of full compensation.

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?

The opening line '发布闲鱼商品' names a specific verb (publish) and resource (Xianyu listing), so an agent immediately knows it creates a live item. It does not differentiate itself from siblings such as edit_item or list_my_items, which is the only thing keeping this from a 5.

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?

The dry_run parameter is the only implicit usage guidance: it says you can pre-check the form without submitting. There is no explicit statement of when to publish versus edit_item, no prerequisites (login/account state), and no warning about creating a real public listing.

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