Skip to main content
Glama

LinkDigest — Xiaohongshu, Douyin, TikTok, YouTube to text

Compare a set of posts in one page

compare_links
Read-only

Read a set of Xiaohongshu, Douyin, Weibo, Hongguo 红果短剧 drama pages, Toutiao 今日头条 links, TikTok, YouTube or X links as one batch and write one comparison over them (批量综合): the themes, hooks, formats and claims they share, the objections readers raise and the gaps none of them cover, every example naming which link it came from and checked against it word for word. The first call starts the batch and returns a batch id; call again with batch_id to collect. Needs an API key. Each link is read at its usual price (cached links are free); the comparison is 1 credit per 10 links. Example: urls=["https://xhslink.com/o/a", "https://xhslink.com/o/b"]. After the browser extension's “Digest the notes on this page” button, call list_batches and pass the newest batch_id here.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "compare_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsNoThe post links, 1 to 20. Required unless batch_id is given.
insightNoAlso draw every post's consumer insight (消费者洞察) and compare on it. +1 credit a link.
batch_idNoCollect a batch still running, instead of urls (re-sending the urls would start it again).
breakdownNoAlso take every post apart (爆款拆解) so the comparison sees each hook and format. +1 credit a link.
translate_toNoWrite the comparison (and each digest) in this language, e.g. en. +1 credit a link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: an asynchronous batch lifecycle, an API key requirement, and a pricing model (each link billed at its usual price, cached links free, comparison at 1 credit per 10 links). It does not state how long a batch takes or how often to re-poll with batch_id, which is the main missing operational detail.

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

Conciseness3/5

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

The purpose and the async contract are front-loaded, but the middle is padded: the long platform enumeration and the clause about every example being 'checked against it word for word' add bulk without much decision value. Several distinct concerns (cost, async, example, extension flow) are packed into one dense block.

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?

With no output schema, the description does describe what the comparison contains and that results are cited per link, plus cost, auth and batching behavior. What is left unstated is the expected wait/polling cadence for collecting a running batch and whether failed links are reported — the remaining gaps are narrow for a 5-param read-only tool.

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

Parameters5/5

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

Schema coverage is already 100%, and the description still adds meaning the schema lacks: the per-link credit surcharge for insight, breakdown and translate_to, and the warning that passing urls instead of batch_id restarts the batch. It also includes a concrete urls example in the expected link format.

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 — read a batch of links from named platforms and write one comparison (批量综合) covering themes, hooks, formats, claims, objections and gaps. The scope (1-20 links, one page, cited per link) makes it clearly distinct from a single-link digest, and it names list_batches for the extension-driven flow.

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?

Explains the two-step usage pattern precisely: first call starts a batch and returns a batch_id, a later call with batch_id collects it, and re-sending urls would restart it. It also explains when to enter this flow (after the extension's 'Digest the notes on this page' button, via list_batches). It does not explicitly say when to prefer this over digest_url for a small number of links, so the alternative routing is only partial.

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.