Skip to main content
Glama
tubearchivist-mcp

tubearchivist-mcp

by si-essence

ta_media

Read-only

Retrieve a video's subtitle track as WebVTT from Tube Archivist by channel ID, video ID, and language for caption processing or transcript access.

Instructions

Subtitle tracks as WebVTT text. Binary media is not exposed. Reads only. Actions: subtitle (GET /media/subtitle/{channel_id}/{video_id}.{lang}.vtt).

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": {
      "action": "<action>"
    },
    "name": "ta_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNolang
actionYesTube Archivist operation to call.
video_idNovideo_id
channel_idNochannel_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered; the description adds real value on top with the return format (WebVTT text), the explicit exclusion of binary payloads, and the underlying endpoint shape. It does not discuss failure modes (e.g., missing subtitle track) or size/limits, keeping it below a 5.

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?

Four short sentences, front-loaded with what the tool returns and what it excludes, with the action map last. Dense and waste-free, though the fragment style ('Reads only.') is slightly telegraphic rather than fully formed prose.

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 correctly shouldered the burden of stating the return type (WebVTT text), and it did. The main remaining gap for a 4-parameter tool is clarifying that the subtitle action consumes channel_id, video_id and lang together, which the URL template implies but never states.

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%, but the schema descriptions merely echo parameter names ('lang', 'video_id', 'channel_id'), so the description's URL template is what actually explains their roles and combined requirement. It still does not state whether lang/channel_id/video_id are mandatory for the subtitle action even though only 'action' is schema-required.

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?

The description gives a concrete resource and return type (subtitle tracks delivered as WebVTT text) plus an explicit non-goal ('Binary media is not exposed'), which effectively separates it from media/download siblings. It is written as telegraphic fragments rather than a full verb-resource statement, and it never names a sibling tool, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'Reads only' and 'Binary media is not exposed' hint that media fetching belongs elsewhere, and the single 'Actions: subtitle' entry shows the only mode. There is no explicit when-to-use statement or named alternative (e.g., ta_download) to route the agent.

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