Skip to main content
Glama

edit_item

Update published Xianyu listings by changing title, description, price, location, condition, delivery, or images; use dry run to preview edits without submitting.

Instructions

编辑已发布商品

Args: item_id: 商品 ID updates: 更新内容,可包含 title/description/price/location/condition/delivery/images 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>",
      "updates": "<updates>"
    },
    "name": "edit_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
item_idYes
updatesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses that dry_run means "only dry-fill, do not actually submit", which is real mutation-safety context, and the updates field list implies partial updates. It says nothing about required permissions, reversibility, or whether list fields like images are replaced or appended — notable gaps for a write operation.

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?

Structured as Args/Returns with a one-line purpose header, which is front-loaded and easy to scan. The only low-value line is "Returns: 编辑结果", which conveys essentially nothing beyond "there is a response".

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 mutation tool with no annotations, no output schema, and a nested `updates` object, the definition covers the basics but omits what an agent most needs to call it safely: partial-update semantics, how nested list fields merge, permission requirements, and failure behavior. Adequate, not complete.

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%, and the description documents all three parameters. Most importantly it enumerates the updatable fields (title/description/price/location/condition/delivery/images) for an `updates` object that the schema leaves as a bare additionalProperties object — genuine added meaning. It falls short of 5 because field types/formats (e.g. price numeric, images array) and `item_id` ("商品 ID") remain tautological.

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 (edit) and resource (published item), and the qualifier "已发布" scopes it to already-published listings, which implicitly separates it from publish_item and delete_item. It does not explicitly name a sibling, so it lands at 4 rather than 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 phrase "已发布商品" implies a precondition (the item must already be published), which is useful implied guidance. However, there is no explicit statement of when to prefer this tool over delete_item or publish_item, and no mention of what to do if the item is not yet published.

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