Analyzes video titles to identify the most common words, helping you understand trending keywords and content patterns in Douyin data.
分析视频标题中的高频词汇
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": "analyze_keywords"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| top_n | No | 返回前N个高频词汇，默认为50 |
Changes observed during successful MCP inspections.
v0.1.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description fails to disclose what the tool returns (e.g., list of words with frequencies), side effects, or prerequisites. It only states the basic operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence (6 words in Chinese) that directly states the function. It could be structured with sections, but it's efficient and front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Missing context: no output schema, no explanation of input source (presumably video titles from previous searches), and no description of return format. The description is insufficient for a tool that likely generates a list of keywords.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with a single parameter described clearly in the schema. The tool description adds no additional semantics beyond what's in the schema, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool analyzes high-frequency words in video titles, distinguishing it from sibling tools that analyze content length or interaction data. However, it doesn't specify which video titles are analyzed (e.g., from a search context), which is a minor gap.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like search_douyin_videos or analyze_content_length. The description lacks context for decision-making.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.