Skip to main content
Glama

LinkDigest — Xiaohongshu, Douyin, TikTok, YouTube to text

by dev.linkdigest
OverviewDiscussionsAdmin

Server Details

Xiaohongshu, Douyin, TikTok, YouTube, X links to text: transcript, on-screen text, images described

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP · MCP 2024-11-05
URL

TDQS

A4.7/5.0

Scored across 1 tool

Disambiguation5/5

With a single tool, there is no risk of confusing it with another. digest_url has a clearly defined purpose and handles all supported inputs through one entry point.

Naming Consistency5/5

digest_url follows a clear verb_noun convention and accurately describes the action. A single tool cannot exhibit mixed naming styles, so the naming pattern is consistent.

Tool Count4/5

One tool is below the typical 3-15 range, but the server's purpose is intentionally narrow: turning any supported URL into digestible text. The single tool earns its place, and additional tools would likely be redundant.

Completeness5/5

The tool covers all advertised platforms plus ordinary web pages and returns the relevant content types: transcript, on-screen text, image descriptions, caption, and metadata. Long-video handling via job_id also prevents dead ends.

Available Tools

1 tool
digest_urlAInspect

Turn a social media URL into LLM-ready context. Works on Xiaohongshu, Douyin, TikTok, YouTube, X and ordinary web pages. Returns the post's transcript, on-screen text, image descriptions, caption and metadata — the things you cannot get by fetching the URL yourself, because these posts are video or images behind tokenised share links. Use this whenever you are given a social media link. Bilibili, Instagram and Facebook are not supported. A long video may not finish in one call: if the result names a job id, call this tool again with that job_id (and no url) to collect it.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesThe post URL, including any share tokens.
formatNomarkdown (default, best for reading) or json (structured).
job_idNoCollect a digest already running. Pass the job id from a previous call instead of url. Use this rather than re-sending the url, which would start the work again.
partial_okNoRead the opening minutes the budget affords instead of refusing a video over max_credits or the plan's length cap. Default false: a long video is refused and costs nothing. When true, the digest carries `partial` (read_seconds, duration_seconds, full_credits).
translate_toNoAlso translate the digest into this language: an ISO 639-1 code, optionally with a region (en, ja, zh-CN). The original-language text is always returned; the translation is added alongside it under `translation` (title, caption, key points, transcript text, on-screen text, image descriptions) — visible in json format. Machine translation. Costs the digest's price plus 1 credit; a repeat of the same url and language is served from cache for free.

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description fully carries behavioral disclosure. It explains why a direct fetch is insufficient (tokenised share links, video/image content), what the output contains, and that long videos may require polling via job_id. This gives the agent a realistic model of the tool's behavior beyond the schema.

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?

The description is compact and front-loaded, with each sentence earning its place: main purpose, supported platforms, return contents, rationale, usage rule, unsupported sites, and async polling behavior. There is no filler or repetition.

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?

Given the absence of an output schema and annotations, the description does a strong job of explaining what results look like and how to handle incomplete jobs. It still leaves some details to the schema (e.g., translate_to costs, partial_ok semantics), but overall an agent has enough to invoke the tool correctly.

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 description coverage is 100%, so the baseline is 3; the schema already thoroughly documents all five parameters. The description adds useful context around job_id and platform support, but does not materially clarify parameter semantics beyond what the schema provides.

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?

The description opens with a specific action ('Turn a social media URL into LLM-ready context') and names the exact resource type and supported platforms (Xiaohongshu, Douyin, TikTok, YouTube, X, ordinary web pages). It also enumerates the returned content, which clearly distinguishes this tool from a simple URL fetcher.

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?

It gives explicit when-to-use guidance ('Use this whenever you are given a social media link'), names unsupported platforms, and explains when to call again with job_id instead of re-sending the URL. This is direct, actionable routing advice with no ambiguity.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changeddigest_url1 field changed
      • addedInput schema / properties / partial_ok
        Added value: +{
+  "description": "Read the opening minutes the budget affords instead of refusing a video over max_credits or the plan's length cap. Default false: a long video is refused and costs nothing. When true, the digest carries `partial` (read_seconds, duration_seconds, full_credits).",
+  "type": "boolean"
+}
  2. 1 tool update
    • Changeddigest_url1 field changed
      • addedInput schema / properties / translate_to
        Added value: +{
+  "description": "Also translate the digest into this language: an ISO 639-1 code, optionally with a region (en, ja, zh-CN). The original-language text is always returned; the translation is added alongside it under `translation` (title, caption, key points, transcript text, on-screen text, image descriptions) — visible in json format. Machine translation. Costs the digest's price plus 1 credit; a repeat of the same url and language is served from cache for free.",
+  "pattern": "^[a-z]{2}(-[A-Z]{2})?$",
+  "type": "string"
+}
  3. 1 tool update
    • First observeddigest_url

Related MCP Connectors

Related MCP Servers

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