SocialDataX 今日头条 MCP

toutiao_search_posts

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

Input Schema

Name	Required	Description	Default
`keyword`	Yes	搜索词或关键词短语，例如 NBA、旅行攻略；不要传作品链接、用户主页链接或内容 ID。
`page_token`	No	首次留空；续页原样传入上一页的 next_page_token，并保持 keyword 不变。

Output Schema

Name	Required	Description
`items`	Yes	当前页内容列表，不包含聚合面板。
`points`	Yes	本次成功调用的积分消耗与账户积分余额。
`next_page_token`	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
```
Changed19 schema fields changedNov 3, 2026
- addedOutput schema / properties / items / items / properties / author / properties / avatar_url / title
```
Added value: +"Avatar Url"
```
- addedOutput schema / properties / items / items / properties / author / properties / name / title
```
Added value: +"Name"
```
- addedOutput schema / properties / items / items / properties / author / properties / profile_url / title
```
Added value: +"Profile Url"
```
- addedOutput schema / properties / items / items / properties / author / properties / user_id / title
```
Added value: +"User Id"
```
- addedOutput schema / properties / items / items / properties / author / title
```
Added value: +"ToutiaoSearchAuthor"
```
- addedOutput schema / properties / items / items / properties / comment_count / title
```
Added value: +"Comment Count"
```
- addedOutput schema / properties / items / items / properties / cover_image_url / title
```
Added value: +"Cover Image Url"
```
- addedOutput schema / properties / items / items / properties / has_video / title
```
Added value: +"Has Video"
```
- addedOutput schema / properties / items / items / properties / like_count / title
```
Added value: +"Like Count"
```
- addedOutput schema / properties / items / items / properties / post_id / title
```
Added value: +"Post Id"
```
- addedOutput schema / properties / items / items / properties / post_url / title
```
Added value: +"Post Url"
```
- addedOutput schema / properties / items / items / properties / publish_time / title
```
Added value: +"Publish Time"
```
- addedOutput schema / properties / items / items / properties / read_count / title
```
Added value: +"Read Count"
```
- addedOutput schema / properties / items / items / properties / summary / title
```
Added value: +"Summary"
```
- addedOutput schema / properties / items / items / properties / title / title
```
Added value: +"Title"
```
- addedOutput schema / properties / items / items / title
```
Added value: +"ToutiaoSearchItem"
```
- addedOutput schema / properties / items / title
```
Added value: +"Items"
```
- addedOutput schema / properties / next_page_token / title
```
Added value: +"Next Page Token"
```
- addedOutput schema / title
```
Added value: +"ToutiaoSearchResult"
```
First observedOct 16, 2026

TDQS

A4.7/5.0

Behavior5/5

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

While annotations provide safety hints, the description adds critical functional behavior by detailing exclusions: it does not return navigation, encyclopedia, user, or video aggregation panels. This defines the output limitations better than metadata alone.

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?

The description is highly efficient. It begins with the core function, immediately clarifies the capability (pagination), and then uses concise, restrictive language to define boundaries without waste.

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

Completeness5/5

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

Given the complexity of the surrounding sibling tools (fetching details, users, etc.), this description is perfectly complete. It establishes the necessary operational boundaries to ensure the agent selects this tool appropriately over any other Toutiao interaction tool.

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?

The input schema coverage is 100%, meaning the schema already provides all technical details for the parameters. The description does not add technical semantic meaning beyond confirming the search behavior defined in the schema.

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

Purpose5/5

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

The description clearly states the primary function: searching for public Toutiao content using keywords or phrases. It distinguishes itself from other search/fetch tools by defining its scope and listing what it does not retrieve.

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

Usage Guidelines5/5

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

It provides perfect usage guidance by specifying that it must be used for keyword or phrase searching. Furthermore, it explicitly outlines usage boundaries by stating it is not intended for retrieving specific link details or finding users, effectively routing the agent away from incorrect sibling calls.

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?