Skip to main content
Glama

SocialDataX 今日头条 MCP

toutiao_get_post_detail_by_url

Read-only

通过头条内容链接或分享文案读取文章、视频或微头条详情;只有内容 ID 时使用 toutiao_get_post_detail_by_post_id。视频说明不是语音转写。

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": {
      "url": "<url>"
    },
    "name": "toutiao_get_post_detail_by_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes头条内容链接或包含该链接的分享文案,支持 /article/ID/、/aID/、/video/ID/ 和 /w/ID/,可取搜索结果 post_url;不要传纯 ID。

Output Schema

NameRequiredDescriptionDefault
titleYes内容标题;无独立标题的微头条可为空,请阅读 content。
videoNo视频播放信息;当前返回无视频信息时省略。
authorYes内容作者,包含作者主页链接。
imagesYes按正文顺序返回的图片,包含链接和像素宽高;无图片时为空数组。
pointsYes本次成功调用的积分消耗与账户积分余额。
contentYes正文纯文本;纯图片内容或视频可能为空,请结合 images 和 video 阅读。视频说明不是语音转写。
post_idYes内容 ID,以字符串表示。
post_urlYes头条内容页面链接。
like_countYes点赞数;未提供时为 null。
read_countYes阅读数;未提供时为 null。
share_countYes分享数;未提供时为 null。
publish_timeYes发布时间,秒级 Unix 时间戳;未提供时为 null。
collect_countYes收藏数;未提供时为 null。
comment_countYes评论数;未提供时为 null。
cover_image_urlYes封面图片链接;未提供时为 null。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / points / description
      Previous value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"
    • changedOutput schema / properties / points / properties / balance / description
      Previous value: -"本次接口完成时看到的当前积分余额,可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时,回退到本次预扣后的余额快照。余额可为负数。"
  2. Changed2 schema fields changed
    • changedOutput schema / properties / points / properties / balance / description
      Previous value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额,可为负数。"
    • removedOutput schema / properties / points / properties / balance / minimum
      Removed value: -0
  3. Changed23 schema fields changed
    • addedOutput schema / properties / author / properties / avatar_url / title
      Added value: +"Avatar Url"
    • addedOutput schema / properties / author / properties / name / title
      Added value: +"Name"
    • addedOutput schema / properties / author / properties / profile_url / title
      Added value: +"Profile Url"
    • addedOutput schema / properties / author / properties / user_id / title
      Added value: +"User Id"
    • addedOutput schema / properties / author / title
      Added value: +"ToutiaoDetailAuthor"
    • addedOutput schema / properties / collect_count / title
      Added value: +"Collect Count"
    • addedOutput schema / properties / comment_count / title
      Added value: +"Comment Count"
    • addedOutput schema / properties / content / title
      Added value: +"Content"
    • addedOutput schema / properties / cover_image_url / title
      Added value: +"Cover Image Url"
    • addedOutput schema / properties / images / items / properties / height / title
      Added value: +"Height"
    • addedOutput schema / properties / images / items / properties / url / title
      Added value: +"Url"
    • addedOutput schema / properties / images / items / properties / width / title
      Added value: +"Width"
    • addedOutput schema / properties / images / items / title
      Added value: +"ToutiaoImageData"
    • addedOutput schema / properties / images / title
      Added value: +"Images"
    • addedOutput schema / properties / like_count / title
      Added value: +"Like Count"
    • addedOutput schema / properties / post_id / title
      Added value: +"Post Id"
    • addedOutput schema / properties / post_url / title
      Added value: +"Post Url"
    • addedOutput schema / properties / publish_time / title
      Added value: +"Publish Time"
    • addedOutput schema / properties / read_count / title
      Added value: +"Read Count"
    • addedOutput schema / properties / share_count / title
      Added value: +"Share Count"
    • addedOutput schema / properties / title / title
      Added value: +"Title"
    • changedOutput schema / properties / video / anyOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "duration_ms": {
      -        "description": "视频时长,单位毫秒。",
      -        "type": "integer"
      -      },
      -      "height": {
      -        "description": "视频高度,像素。",
      -        "type": "integer"
      -      },
      -      "video_url": {
      -        "description": "视频播放链接,有效期有限,建议获取后及时使用。",
      -        "type": "string"
      -      },
      -      "width": {
      -        "description": "视频宽度,像素。",
      -        "type": "integer"
      -      }
      -    },
      -    "required": [
      -      "video_url",
      -      "duration_ms",
      -      "width",
      -      "height"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "duration_ms": {
      +        "description": "视频时长,单位毫秒。",
      +        "title": "Duration Ms",
      +        "type": "integer"
      +      },
      +      "height": {
      +        "description": "视频高度,像素。",
      +        "title": "Height",
      +        "type": "integer"
      +      },
      +      "video_url": {
      +        "description": "视频播放链接,有效期有限,建议获取后及时使用。",
      +        "title": "Video Url",
      +        "type": "string"
      +      },
      +      "width": {
      +        "description": "视频宽度,像素。",
      +        "title": "Width",
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "video_url",
      +      "duration_ms",
      +      "width",
      +      "height"
      +    ],
      +    "title": "ToutiaoVideoData",
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedOutput schema / title
      Added value: +"ToutiaoDetailResult"
  4. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful content caveat — that the video description field is not a speech transcription — which prevents misinterpretation of returned data, but says nothing about pagination, error behavior, or fetch limits. Modest added value beyond annotations.

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 compact clauses: capability plus routing first, then a single disambiguation note about video descriptions. No filler and the most decision-relevant information is front-loaded.

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?

For a single-parameter read tool with full schema coverage, a detailed url description, an output schema, and read-only annotations, nothing needed to call it correctly is missing. The sibling routing and the video-field caveat close the remaining ambiguity.

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 100% and the url parameter's schema description already documents accepted path forms and the 'do not pass a bare ID' rule. The description's mention of share text and link merely restates what the schema says, adding no new syntax or format detail, so the baseline 3 applies.

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 names a specific verb and resource set — reading article, video, or weitaotiao detail — and pins the input mode to a content link or share text. It also distinguishes itself from the sibling that takes an ID, so an agent can choose without opening either schema.

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?

Explicit routing rule: when only a content ID is available, use toutiao_get_post_detail_by_post_id instead. Combined with the URL-based input constraint, the when-to-use and when-not-to-use conditions are both stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources