SocialDataX 今日头条 MCP

toutiao_search_suggestions

Read-only

获取今日头条搜索输入框的联想词；不返回用户或内容详情，不支持分页。

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": {
      "keyword": "<keyword>"
    },
    "name": "toutiao_search_suggestions"
  }
}

Input Schema

Name	Required	Description	Default
`keyword`	Yes	搜索关键词或短语，例如美食、旅行；不要传链接、用户 ID 或 page_token。

Output Schema

Name	Required	Description	Default
`items`	Yes	搜索建议列表；无匹配建议时为空数组。
`points`	Yes	本次成功调用的积分消耗与账户积分余额。

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

changedOutput schema / properties / points / description

Previous value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"

changedOutput schema / properties / points / properties / balance / description

Previous value: -"本次接口完成时看到的当前积分余额，可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时，回退到本次预扣后的余额快照。余额可为负数。"

Changed2 schema fields changedNov 4, 2026
- changedOutput schema / properties / points / properties / balance / description
```
Previous value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额，可为负数。"
```
- removedOutput schema / properties / points / properties / balance / minimum
```
Removed value: -0
```
Changed4 schema fields changedNov 3, 2026
- addedOutput schema / properties / items / items / properties / text / title
```
Added value: +"Text"
```
- addedOutput schema / properties / items / items / title
```
Added value: +"ToutiaoSearchSuggestionItem"
```
- addedOutput schema / properties / items / title
```
Added value: +"Items"
```
- addedOutput schema / title
```
Added value: +"ToutiaoSearchSuggestionsResult"
```
First observedOct 16, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The annotations already establish that this is a read-only, open-world operation. The description adds that results are non-paginated and limited to suggestion strings rather than entities, which is useful context, but it says nothing about result volume or rate limits that an agent would otherwise need.

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

Conciseness5/5

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

Two short clauses separate the resource description from the constraints, with no filler. The primary purpose is stated first, followed by the limits.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema and full annotation coverage, the description is essentially complete: an agent knows what it gets and that it cannot paginate. It is slightly thin on when to choose this over the other search tools, which keeps it from a 5.

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?

With one parameter at 100% schema coverage, the keyword parameter and its exclusions are already fully documented in the schema, so the description provides no further specification. The baseline of 3 holds because the schema does all the work.

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 says the tool fetches autocomplete suggestions from the Toutiao search box, a verb+resource statement specific enough to distinguish it from sibling content tools. The added negations (no user or content details) reinforce what it is not, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Does not return user or content details' and 'no pagination' effectively tell the agent when to route elsewhere, such as toutiao_search_users or toutiao_search_posts, but the description never names those alternatives or states the positive trigger for using this tool.

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

All SocialDataX 今日头条 MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?