Skip to main content
Glama

Read a video or channel to make one like it

read_youtube_link

Reads a YouTube or TikTok video link, or a YouTube channel link, for "make one like this": how the video is built (hook, structure, ending, narration, length, title pattern, closest ClipFlux look) and fresh topics in the same format; for a channel, what it is about, its title pattern and its best recent video read the same way. A video costs about 3 credits, a channel about 4; the result says how much. Then draft_video with likeUrl (the video, or the channel's best video) makes a new video in that format, never copying its words.

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": {
      "url": "<url>"
    },
    "name": "read_youtube_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe video or channel link the user gave.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing credit cost (about 3 for a video, 4 for a channel), that the cost is reported in the result, that it fetches external open-world content, and that the downstream video never copies the source's words. This squares with readOnlyHint=false, since credits are consumed. What is missing is failure behavior for private, region-locked, or invalid links, and whether a failed read still charges.

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 the verb and the payload list, and every clause carries real information (output contents, channel case, credits, handoff). The channel clause — "for a channel, what it is about, its title pattern and its best recent video read the same way" — is tangled enough to slow parsing on first read.

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 and only one parameter, the description carries the burden and does it: it describes the shape of the returned analysis, the channel variant, and the cost field. Only edge cases (invalid/private links, partial failures) are unaddressed, which is minor for a read tool.

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?

The single parameter is fully documented in the schema (coverage 100%), so the baseline is 3. The description only adds that the same field accepts TikTok links and channel links, a small clarification rather than new syntax or format guidance.

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 ("Reads") plus the exact resource set (YouTube/TikTok video link, YouTube channel link) and enumerates what the read produces: hook, structure, ending, narration, length, title pattern, closest ClipFlux look, and fresh topics. It also names the sibling it hands off to (draft_video with likeUrl), so an agent can separate it from get_video, quote_video, or draft_video without opening any schema.

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?

Frames the use case as the "make one like this" workflow and explicitly states the next step: draft_video with likeUrl (the video, or the channel's best video). It does not, however, say when NOT to use it — e.g. when a link should go to get_video or quote_video instead — so the routing against those siblings is left implicit.

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.

Resources