Skip to main content
Glama

search_items

Search Xianyu listings by keyword, filtering by price range, location, and sort order to return matching products for quick comparison.

Instructions

搜索闲鱼商品(带错误恢复)

Args: keyword: 搜索关键词 price_min: 最低价格 price_max: 最高价格 location: 地区筛选 sort_by: 排序方式 (default, price_asc, price_desc, sales) limit: 返回数量限制

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": {
      "keyword": "<keyword>"
    },
    "name": "search_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
keywordYes
sort_byNodefault
locationNo
price_maxNo
price_minNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It discloses only that the tool has 'error recovery', with nothing about authentication, rate limits, pagination, or how results are ordered when sort_by is left at 'default' – meaningful gaps for a network-backed search 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 is front-loaded in one line, followed by a compact, scannable Args list. The trailing 'Returns: item list' is near-zero value and the '(with error recovery)' aside is vague, but there is no padding overall.

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 six-parameter, no-output-schema, no-annotation search tool, parameter coverage is good but the return side is reduced to 'a list of items' – no field descriptions, no pagination or total-count behavior. An agent can call it correctly but cannot anticipate the shape or volume of results.

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%, so the description must compensate, and it does: all six parameters are explained (keyword, price_min/max, location, sort_by, limit). It crucially enumerates the accepted sort_by values (default, price_asc, price_desc, sales), which the schema itself does not, though it omits the default value of limit (20) and the meaning of 'default' sorting.

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 first line states a specific verb and resource: search Xianyu (Idle Fish) product listings by keyword. That is enough to distinguish it from siblings like get_top_items or list_my_items, though the description never names or contrasts those alternatives explicitly.

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

Usage Guidelines2/5

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

There is no guidance on when to use this search versus get_top_items, list_my_items, or analyze_competitors, and no prerequisites or exclusions are stated. The only contextual hint is the parenthetical 'with error recovery', which does not tell an agent when this tool is the right choice.

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