Skip to main content
Glama

get_top_items

Retrieves ranked Xianyu product listings by sales, views, or wants, with a configurable result limit for market trend and demand analysis.

Instructions

获取热门商品排行

Args: limit: 返回数量 sort_by: 排序方式 (sales, views, wants)

Returns: 商品列表

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_top_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sort_byNosales

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does say the return is a list of items, but it omits the ranking window (top over what period? all time?), whether results are scoped to the caller's own items or the whole marketplace, pagination, and any permission requirements.

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?

It is short, front-loaded with the purpose, and structured with Args and Returns blocks. The Args lines are terse but there is no filler to remove; the only weakness is that brevity comes at the cost of detail rather than being over-verbose.

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 simple two-parameter read tool with no output schema, the description covers purpose, both inputs and the return kind. It still leaves a meaningful gap: the notion of 'top' has no time window or scope statement, which is the main thing an agent needs to interpret the results correctly.

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

Parameters3/5

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

Schema coverage is 0%, so the description must compensate and partially does: it names the sort_by enum values (sales, views, wants), which appear nowhere in the schema and materially change behavior. However, limit is only glossed as '返回数量' with no range or cap, and the schema default of 10 for limit and 'sales' for sort_by are not mentioned.

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 description states a specific verb and resource: retrieve a ranking of popular items (获取热门商品排行). That is clear enough for an agent to know what the tool returns, but it never distinguishes this from siblings like search_items, list_my_items or get_item_analytics, and 'popular/top' is left undefined except implicitly by the sort_by default.

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 tool versus the alternatives (search_items, list_my_items), no prerequisites, and no exclusions. The Args section documents inputs only; nothing tells an agent which situation selects this tool.

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