Skip to main content
Glama

LinkDigest — Xiaohongshu, Douyin, TikTok, YouTube to text

by dev.linkdigest
OverviewDiscussionsAdmin

Find posts on a topic

search_links
Read-only

Find posts on a topic on xiaohongshu, douyin, youtube, x, web (web search scoped to the platform, filtered to links digest_url can read). A search that finds posts costs 4 credits on douyin and xiaohongshu, 1 elsewhere; nothing found is free. Searching is metered by credits, not by an hourly count. Returns a numbered list; pass digest: true to read them as one batch and compare them (then compare_links with the batch_id). xiaohongshu returns the notes the web has indexed, read from their public pages (no login, no session); for the user's own feed or a search the web has not seen, they press the extension's “Digest the notes on this page” button on the page they see, then list_batches. douyin returns the video pages the web has indexed, each read through Douyin's own embed player like a pasted link; Chinese words find the most. Needs an API key. Example: query="护肤 早C晚A", platform="xiaohongshu", limit=5.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many links, 1 to 10 (default 5).
queryYesThe topic, in any language.
digestNoAlso read the results as one batch with a comparison (批量综合); returns the batch_id for compare_links.
insightNoWith digest: draw every post's consumer insight (消费者洞察), +1 credit a link.
platformYesWhere to look: xiaohongshu, douyin, youtube, x, web.
breakdownNoWith digest: take every post apart (爆款拆解), +1 credit a link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / platform / description
      Previous value: -"Where to look: xiaohongshu, youtube, x, web."New value: +"Where to look: xiaohongshu, douyin, youtube, x, web."
    • changedInput schema / properties / platform / enum
      Previous value: -[
-  "xiaohongshu",
-  "youtube",
-  "x",
-  "web"
-]New value: +[
+  "xiaohongshu",
+  "douyin",
+  "youtube",
+  "x",
+  "web"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / platform / description
      Previous value: -"Where to look: youtube, x, web."New value: +"Where to look: xiaohongshu, youtube, x, web."
    • changedInput schema / properties / platform / enum
      Previous value: -[
-  "youtube",
-  "x",
-  "web"
-]New value: +[
+  "xiaohongshu",
+  "youtube",
+  "x",
+  "web"
+]
  3. Added

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the readOnly/openWorld/idempotent annotations by disclosing the credit cost model per platform, that 'nothing found is free', metered-by-credits rather than hourly limits, and that an API key is required. Also explains the no-login public-page read path for xiaohongshu and the embed-player read for douyin. Slightly dense but covers the traits an agent needs.

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?

Front-loaded with purpose, then cost, then per-platform behavior and an example — a sensible order. It is longer than typical and the platform-specific details run together, but nearly every sentence carries actionable information.

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?

Covers purpose, cost, auth, platform-specific limitations, the digest→compare_links workflow, and a worked example, which is everything needed to call a metered search tool with no output schema. No material gaps remain.

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 baseline is 3; the description adds workflow-level meaning by tying digest: true to the compare_links follow-up via batch_id, and gives a concrete example query/platform/limit set. It does not explain insight/breakdown, but the schema already documents those.

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?

Opens with a specific verb+resource ('Find posts on a topic') and immediately enumerates the five platforms searched, so an agent knows exactly what this returns without opening the schema. It is clearly distinct from siblings like digest_url (reads a single link) and compare_links (compares a batch).

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?

States explicit routing: pass digest: true to read results as one batch and then use compare_links with the batch_id. It also gives a concrete alternative path when xiaohongshu lacks web-indexed coverage (extension button, then list_batches), and notes douyin's Chinese-language query effectiveness.

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

All LinkDigest — Xiaohongshu, Douyin, TikTok, YouTube to text toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources