Skip to main content
Glama

Video Transcript MCP for TikTok, Instagram Reels & YouTube — Mira

Watch a video link

parse_video
Read-only

Watch a TikTok, Instagram Reel, YouTube Short/video, Pinterest, Facebook or X video link (or a web page) and return its transcript, on-screen text, caption and a structured extract. On the Extract + Video plan it also returns a download link for the original video (every file of a carousel). If the result isn't ready yet, returns a job_id.

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": "parse_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe video or page link

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuinely non-schema behavior: plan-gated download links (Extract + Video plan), carousel handling returning every file, and an asynchronous job_id path. These are real operational traits the agent could not derive from the schema or annotations. It still doesn't say how long jobs take or how to poll.

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?

Three sentences, front-loaded with the core action and platform scope before the plan-dependent and async caveats. Every clause contributes; the platform enumeration is long but necessary to scope inputs, and 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?

There is no output schema, so the description correctly spends its space enumerating return values (transcript, on-screen text, caption, structured extract, download link, job_id). For a one-parameter tool that is nearly complete; the missing piece is the continuation path after a job_id is returned.

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?

With a single parameter at 100% schema description coverage, the schema already carries the semantics, so the baseline of 3 applies. The description does add one useful clarification — the url may be a web page as well as a video link — but nothing about format, redirects, or platform-specific URL shapes.

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?

Opens with a concrete verb and resource ('Watch a ... video link') and enumerates supported platforms plus the returned artifacts (transcript, on-screen text, caption, structured extract), so the agent knows exactly what the tool produces. It stops short of naming get_result as the counterpart when a job_id comes back, leaving sibling differentiation implicit rather than stated.

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?

The mention that an unready result returns a job_id implies a follow-up retrieval step, and the platform list implies accepted input scope, but the description never states 'call this when you have a video URL and want its content' or directs the agent to get_result to resolve the job_id. Usage is inferable but not explicit, and no when-not-to-use case is given.

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.