Skip to main content
Glama
Sign In

Finewisdom 社媒与电商数据接口

by io.github.yy05idiot
OverviewDiscussionsAdmin

weibo_sub_comments

Read-onlyIdempotent

获取微博评论的回复列表。返回二级评论的正文、点赞数、回复者信息与时间。追踪评论区的二次讨论与争议点时用，需先拿到主评论ID。单价¥0.2/次，仅成功调用计费，失败或空结果自动退回。

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": {
      "comment_id": "<comment_id>"
    },
    "name": "weibo_sub_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
_tokenNo备用鉴权：fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
comment_idYes评论ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description still adds genuinely new behavior: per-call pricing (¥0.2), that billing only occurs on success, and that failures or empty results are auto-refunded. The prerequisite dependency on a main comment ID is also a workflow constraint absent from the structured fields.

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?

Three compact sentences ordered purpose → use case/prerequisite → cost model, with no filler or repetition. Each sentence carries information an agent cannot get from the schema or annotations.

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?

There is no output schema, but the description compensates by listing the return fields, and it additionally covers the cost/refund model and the ID prerequisite. For a simple two-parameter read tool, nothing needed for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the two parameters are already documented, which sets the baseline at 3. The description adds meaningful semantics by clarifying that comment_id must specifically be a main/top-level comment ID, which the schema's bare "评论ID" does not convey; the _token parameter's header alternative is left entirely to 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?

States a specific verb and resource ("获取微博评论的回复列表") and immediately qualifies the resource as second-level/sub-comments, which distinguishes it from the sibling weibo_post_comments. It also enumerates the returned fields (正文、点赞数、回复者信息、时间), so an agent knows exactly what it gets.

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?

Gives an explicit use case (tracking secondary discussion and controversy points in comment sections) plus a hard prerequisite (must first obtain the main comment ID). It does not name weibo_post_comments as the explicit alternative for the main-comment tier, so it falls short of a full when/when-not routing statement.

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

All Finewisdom 社媒与电商数据接口 toolsInspect
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