Skip to main content
Glama

SocialDataX 微信 WeChat MCP

wechat_get_video_share_url_by_object_id

Read-only

根据微信视频号作品 object_id 获取分享链接;只接受数值 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>"
    },
    "name": "wechat_get_video_share_url_by_object_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
object_idYes微信视频号作品的 object_id,例如 15011178920418020652;用户已提供时直接使用,否则可从作品详情或用户发布作品列表结果获取;不要传 encrypted_object_id 或作品链接。

Output Schema

NameRequiredDescriptionDefault
pointsYes本次成功调用的积分消耗与账户积分余额。
share_urlYes微信视频号作品分享链接

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. Changed2 schema fields changed
    • addedOutput schema / properties / share_url / title
      Added value: +"Share Url"
    • addedOutput schema / title
      Added value: +"WechatVideoShareUrlResult"
  4. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds one behavioral constraint — the tool only accepts a numeric object_id, implying non-numeric input is rejected — but says nothing about link lifetime, permissions, or failure behavior.

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 front-loaded clause pairing the action with the input constraint; no filler. It is minimal but not misleadingly terse for a one-parameter read operation.

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

Completeness3/5

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

With one required parameter, full schema coverage, annotations, and an output schema, the description covers the essentials. It stops short of routing the agent among the numerous sibling tools that also accept an object_id or URL.

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 object_id property description already explains format, example value, where to obtain it, and that encrypted_object_id or a video URL must not be passed. The tool description only echoes the numeric-only rule, adding no meaning beyond the schema.

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 verb and resource: retrieve a share link (分享链接) for a WeChat Channels video work identified by object_id. This is distinguishable from sibling tools like wechat_get_video_detail_by_object_id, though the description never explicitly contrasts them.

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

Usage Guidelines3/5

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

Usage is implied by the resource (call it when you need a share URL), but there is no explicit when/when-not guidance and no mention of the many sibling by_object_id / by_url / by_encrypted_object_id variants that an agent might otherwise pick.

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