Skip to main content
Glama

get_traffic_analytics

Fetch traffic statistics for a specified number of days to review Xianyu listing performance and track changes in views or visits.

Instructions

获取流量统计

Args: days: 统计天数

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_traffic_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo

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 provided, so the description carries the full behavioral burden and mostly fails it. '获取' implies a read-only query, but there is nothing about permissions, aggregation behavior, timezone or date boundaries for the window, or what the statistics actually contain.

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?

It is short and front-loads the purpose, but the docstring scaffolding (Args / Returns) is wasted space: the Args line duplicates the schema and the Returns line ('流量统计数据') restates the tool name without conveying anything.

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?

The tool is simple with one optional parameter and no output schema, so the description did not need to be long, but it should have clarified the default window and the shape of the returned statistics. As written, an agent knows almost nothing it could not read from the schema.

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%, and the only parameter note, '统计天数', merely restates the schema title 'Days' without adding meaning. It omits the default of 7 and does not say whether the window is calendar days, rolling days, or inclusive of today.

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 and a resource, but 'traffic' is left unscoped, so an agent cannot tell whether this covers item traffic, store traffic, or referral traffic, and nothing distinguishes it from siblings such as get_item_analytics or get_sales_analytics. The purpose is implied rather than pinned down.

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?

The description gives no when-to-use guidance, no prerequisites, and no alternatives. With multiple analytics siblings available, the agent is left to guess which one this is for.

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