Skip to main content
Glama

analyze_competitors

Analyzes competitor listings from provided Xianyu item IDs, returning comparison insights to support pricing and product decisions.

Instructions

分析竞品商品

Args: item_ids: 竞品商品 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_ids": "<item_ids>"
    },
    "name": "analyze_competitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/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 behavioral burden, and it discloses almost nothing: no cost, latency, rate limit, auth requirement, or whether an external data source is queried. The 'Returns: 竞品分析结果' line is a pure restatement of the tool name with no output detail, and there is no output schema to compensate.

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 text is short and front-loads the purpose, which is good, but it is structured as boilerplate Args/Returns scaffolding where the Returns section conveys no information. It is under-specified rather than bloated.

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 a tool with no annotations, no output schema, and an undocumented sole parameter, the description leaves the agent unable to predict cost, result shape, or failure modes. A one-line statement of what the analysis covers and what it returns would have closed most of the gap.

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% and the schema only says 'array of items', so the note that item_ids is a list of competitor product IDs does add genuine meaning beyond the schema. However, no ID format, size limit, or validity/error behavior is described, so the compensation is partial.

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?

The description ('分析竞品商品') names a verb and a resource, but it essentially restates the tool name analyze_competitors in Chinese. It gives no indication of what the analysis produces (pricing? ranking? reviews?) or how it differs from siblings such as get_item_analytics or get_top_items.

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 prerequisites, and no mention of alternatives. Critically, nothing tells the agent whether the IDs refer to competitor listings rather than the user's own items (list_my_items / get_item_analytics exist as siblings), which is the main routing decision an agent must make here.

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