Skip to main content
Glama
Sign In

Finewisdom 社媒与电商数据接口

by io.github.yy05idiot
OverviewDiscussionsAdmin

tiktok_sub_comments

Read-onlyIdempotent

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

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive, so the description correctly spends its budget elsewhere: it discloses the return payload (正文、点赞数、回复者信息、时间) and the full billing model — ¥0.1 per call, charged only on success, auto-refunded on failure or empty results. Cost/refund behaviour is not derivable from any structured field and is genuinely load-bearing for call decisions.

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?

Four compact sentences ordered as purpose → return shape → usage prerequisite → cost model, with zero filler or repetition of schema content. Every sentence carries information an agent needs before calling.

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 two-required-param read-only tool with 100% schema coverage and no output schema, the description covers what it returns, when to use it, the prerequisite, and the cost consequence of failure — nothing material 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% with per-field descriptions, so baseline is 3; the description adds real meaning by specifying that comment_id must be a *main* comment ID (not any arbitrary reply), which the schema's bare '评论ID' does not convey. No added detail on _token or format expectations 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+resource ('获取TikTok评论回复') and then pins the scope precisely with '二级评论' and the field list (正文、点赞数、回复者信息、时间), which separates it from top-level comment tools like tiktok_post_comments. It does not name that sibling outright, so the sibling differentiation is left implicit through '需先拿到主评论ID' rather than explicit routing.

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 a concrete use case, and '需先拿到主评论ID' states the prerequisite ordering that forces the agent to call the parent comment tool first. No explicit when-not guidance or named alternative (e.g. tiktok_post_comments) is given, which keeps it short of a 5.

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