Skip to main content
Glama

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

Get video extract

get_result
Read-only

Get the extract of a video that was still processing, by its 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": {
      "job_id": "<job_id>"
    },
    "name": "get_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job_id of the video being processed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description only needs to add job-lifecycle semantics. It hints that the video "was still processing" but never says whether the call blocks, errors, or returns partial data while processing, which is the key behavioral question for a job-result endpoint.

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?

One compact sentence with the resource and the key identifier front-loaded and no filler. Phrasing is slightly awkward ("was still processing") but nothing is wasted.

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?

For a one-parameter read tool with a fully documented schema and a readOnly annotation, the description covers the essentials. The remaining gap is that "extract" is undefined and there is no output schema, so the agent cannot know whether it receives a transcript, frames, or metadata.

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% and the single job_id parameter is documented in the schema, so the description adds nothing beyond it. Baseline 3 is appropriate here.

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?

States a specific verb and resource ("Get the extract of a video") scoped to a condition ("that was still processing") and keyed by job_id, so an agent can tell it apart from parse_video, which presumably starts the job. It never names a sibling explicitly, so the differentiation is inferred from the async framing 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 phrase "that was still processing" implies this is the follow-up call for a job submitted earlier, which is useful context. It never says whether to poll, how often, or what to do if the job is not yet finished, so the when-to-use guidance stops at implication.

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.