Skip to main content
Glama

get_item_analytics

Fetch item statistics by Xianyu item ID to assess listing performance and support product research.

Instructions

获取商品统计数据

Args: item_id: 商品 ID

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>"
    },
    "name": "get_item_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 disclosure burden, yet it says nothing about read-only behavior, permissions, rate limits, data freshness, or what the returned statistics contain. The single line "Returns: 商品统计数据" merely restates the purpose rather than adding behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded with the purpose, which is good. But the Args/Returns block is pure boilerplate that duplicates the schema and the purpose line without contributing information, so the brevity reflects under-specification rather than efficient density.

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 an analytics tool with no annotations and no output schema, the description should explain what statistics are returned and what the item_id refers to. Instead it leaves the return payload entirely opaque, which is inadequate given the presence of multiple overlapping analytics siblings.

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

Parameters2/5

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

Schema description coverage is 0% for the one parameter, so the description must compensate, but "item_id: 商品 ID" only repeats the schema title "Item Id" with no format, source, or constraints (e.g., whether it is a numeric ID, a marketplace SKU, or how to obtain it). No meaning is added beyond the structured field.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"获取商品统计数据" states a verb (get) and resource (item statistics), so the basic action is identifiable. However, it never specifies what statistics (sales? traffic? conversions?) are returned, and it does not distinguish this from siblings such as get_sales_analytics, get_traffic_analytics, or get_top_items, leaving the agent to guess which analytics tool applies.

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 when-to-use guidance, no exclusions, and no mention of when an agent should pick this over the several other analytics siblings. The only usage signal is the required item_id, which is inferable from the schema anyway.

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