Skip to main content
Glama

SocialDataX 微信 WeChat MCP

wechat_get_video_comments_by_object_id

Read-only

已有同一条视频的 object_id 和 object_nonce_id 时获取评论列表;用户已提供合法组合时直接使用,否则可从作品详情结果或一级评论结果获取;搜索结果只有 encrypted_object_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": {
      "object_id": "<object_id>",
      "object_nonce_id": "<object_nonce_id>"
    },
    "name": "wechat_get_video_comments_by_object_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
object_idYes微信视频号视频的 object_id,例如 14882122090270235141;用户已提供时直接使用,否则可从作品详情或一级评论结果获取;获取评论或评论回复时请与同一条视频的 object_nonce_id 一起原样传入。
page_tokenNo评论分页令牌;首次请求留空,继续翻页时必须将上一页返回的完整 next_page_token 原样传回。
object_nonce_idYes微信视频号视频的 object_nonce_id,例如 12801331239707625908_0_39_0_0;用户已提供时直接使用,否则可从作品详情或一级评论结果获取;获取评论或评论回复时请与同一条视频的 object_id 一起原样传入。

Output Schema

NameRequiredDescriptionDefault
itemsYes当前页评论列表;过滤后可能为空数组
pointsYes本次成功调用的积分消耗与账户积分余额。
comment_countYes评论总数
next_page_tokenYes下一页不透明分页令牌;为空表示没有更多评论。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回;next_page_token 只能用于同一微信视频号评论分页链路;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容。

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 / comment_count / title
      Added value: +"Comment Count"
    • addedOutput schema / properties / items / items / properties / author / properties / avatar_url / title
      Added value: +"Avatar Url"
    • addedOutput schema / properties / items / items / properties / author / properties / has_wechat_channels_account / title
      Added value: +"Has Wechat Channels Account"
    • addedOutput schema / properties / items / items / properties / author / properties / name / title
      Added value: +"Name"
    • 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: +"WechatVideoCommentAuthorData"
    • addedOutput schema / properties / items / items / properties / comment_id / title
      Added value: +"Comment Id"
    • addedOutput schema / properties / items / items / properties / content / title
      Added value: +"Content"
    • addedOutput schema / properties / items / items / properties / image_urls / title
      Added value: +"Image Urls"
    • addedOutput schema / properties / items / items / properties / ip_location / title
      Added value: +"Ip Location"
    • addedOutput schema / properties / items / items / properties / like_count / title
      Added value: +"Like Count"
    • addedOutput schema / properties / items / items / properties / object_id / title
      Added value: +"Object Id"
    • addedOutput schema / properties / items / items / properties / object_nonce_id / title
      Added value: +"Object Nonce Id"
    • addedOutput schema / properties / items / items / properties / publish_time / title
      Added value: +"Publish Time"
    • addedOutput schema / properties / items / items / properties / reply_count / title
      Added value: +"Reply Count"
    • addedOutput schema / properties / items / items / properties / stickers / items / properties / thumbnail_url / title
      Added value: +"Thumbnail Url"
    • addedOutput schema / properties / items / items / properties / stickers / items / properties / url / title
      Added value: +"Url"
    • addedOutput schema / properties / items / items / properties / stickers / items / title
      Added value: +"WechatVideoCommentStickerData"
    • addedOutput schema / properties / items / items / properties / stickers / title
      Added value: +"Stickers"
    • addedOutput schema / properties / items / items / title
      Added value: +"WechatVideoCommentItemData"
    • 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: +"WechatVideoCommentsResult"
  4. Changed2 schema fields changed
    • addedOutput schema / properties / items / items / properties / image_urls
      Added value: +{
      +  "description": "评论图片完整链接列表;没有时为空数组。链接可能失效,有效期未知;需长期保存时及时下载,图片格式以文件内容为准。",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / items / items / properties / stickers
      Added value: +{
      +  "description": "评论表情包列表;按原顺序返回,没有时为空数组",
      +  "items": {
      +    "properties": {
      +      "thumbnail_url": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "description": "表情包缩略图链接;没有时为 null;链接可能失效,有效期未知"
      +      },
      +      "url": {
      +        "description": "表情包原图链接;可能是静态图片或动图。链接可能失效,有效期未知;需长期保存时及时下载,图片格式以文件内容为准。",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "url"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  5. Changed1 schema field changed
    • addedOutput schema / properties / items / items / properties / author / properties / has_wechat_channels_account
      Added value: +{
      +  "default": false,
      +  "description": "是否开通微信视频号",
      +  "type": "boolean"
      +}
  6. Changed3 schema fields changed
    • changedInput schema / properties / object_id / description
      Previous value: -"微信视频号视频的 object_id,例如 14882122090270235141;获取评论或评论回复时请与同一条视频的 object_nonce_id 一起原样传入。"New value: +"微信视频号视频的 object_id,例如 14882122090270235141;用户已提供时直接使用,否则可从作品详情或一级评论结果获取;获取评论或评论回复时请与同一条视频的 object_nonce_id 一起原样传入。"
    • changedInput schema / properties / object_nonce_id / description
      Previous value: -"微信视频号视频的 object_nonce_id,例如 12801331239707625908_0_39_0_0;获取评论或评论回复时请与同一条视频的 object_id 一起原样传入。"New value: +"微信视频号视频的 object_nonce_id,例如 12801331239707625908_0_39_0_0;用户已提供时直接使用,否则可从作品详情或一级评论结果获取;获取评论或评论回复时请与同一条视频的 object_id 一起原样传入。"
    • changedOutput schema / properties / items / items / properties / comment_id / description
      Previous value: -"评论 ID"New value: +"微信视频号一级评论 ID;可作为评论回复工具的 comment_id 输入。"
  7. Changed2 schema fields changed
    • changedInput schema / properties / object_id / description
      Previous value: -"微信视频号视频的 object_id,例如 14882122090270235141;获取评论时请与同一条视频的 object_nonce_id 一起原样传入。"New value: +"微信视频号视频的 object_id,例如 14882122090270235141;获取评论或评论回复时请与同一条视频的 object_nonce_id 一起原样传入。"
    • changedInput schema / properties / object_nonce_id / description
      Previous value: -"微信视频号视频的 object_nonce_id,例如 12801331239707625908_0_39_0_0;获取评论时请与同一条视频的 object_id 一起原样传入。"New value: +"微信视频号视频的 object_nonce_id,例如 12801331239707625908_0_39_0_0;获取评论或评论回复时请与同一条视频的 object_id 一起原样传入。"
  8. Changed2 schema fields changed
    • addedOutput schema / properties / points
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "本次成功调用的积分消耗与调用完成时的账户积分余额。",
      +  "properties": {
      +    "balance": {
      +      "description": "本次接口完成时看到的当前积分余额。",
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "cost": {
      +      "description": "本次请求最终确认消耗的积分。",
      +      "minimum": 0,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "cost",
      +    "balance"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "items",
      -  "next_page_token",
      -  "comment_count"
      -]New value: +[
      +  "items",
      +  "next_page_token",
      +  "comment_count",
      +  "points"
      +]
  9. Changed1 schema field changed
    • changedOutput schema / properties / items / items / properties / author / properties / user_id / description
      Previous value: -"评论作者微信视频号用户 ID;可能是 @finder 或 @stranger;仅 @finder 可用于用户信息工具;不可用时为空字符串"New value: +"评论作者微信视频号用户 ID;可能是 @finder 或 @stranger;仅 v2_...@finder 可用于用户信息工具;不可用时为空字符串"
  10. Changed2 schema fields changed
    • addedOutput schema / properties / comment_count
      Added value: +{
      +  "description": "评论总数",
      +  "type": "integer"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "items",
      -  "next_page_token"
      -]New value: +[
      +  "items",
      +  "next_page_token",
      +  "comment_count"
      +]
  11. First observed

TDQS

A3.9/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. The description adds prerequisite and input-acquisition constraints, but does not disclose rate limits, permission requirements, or other operational behavior. An output schema exists, so return-value details are not required here.

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

Conciseness4/5

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

A single compact, semicolon-delimited sentence front-loads the direct-use condition and then gives fallback paths. It is dense but has no unnecessary wording.

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?

Covers how to obtain the required IDs and the dependency on the detail tool when only encrypted_object_id exists, while the schema handles pagination and annotations cover safety. It is nearly complete for a comment-list tool with an output schema, though it does not explicitly clarify whether replies are excluded or what the list scope is.

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 description coverage is 100%, and the parameter schema already explains object_id/object_nonce_id pairing and page_token handling. The description reinforces the same-video requirement and ID sourcing, but adds little parameter meaning beyond what the schema already provides.

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?

States a specific action, '获取评论列表', for the same video's comments scoped by object_id and object_nonce_id. The ID-pair requirement and encrypted_object_id fallback make its role distinguishable, though it does not explicitly name the URL-based comments sibling as an alternative.

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?

Gives an explicit workflow: if the user already supplied a valid ID pair, use it directly; otherwise obtain the pair from work-detail results or first-level comment results; if search results only contain encrypted_object_id, call the detail tool first. This covers when to use it and what to do instead.

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