Skip to main content
Glama

instagram: Reel or video transcript

instagram_transcript
Read-only

Reel or video transcript. The caption track Instagram published for a reel or video, as one text block plus timed cues. This is Instagram's own track, never a transcription of the audio, so a transcript here is what the platform published rather than what a model guessed. Instagram has published no caption track on any reel checked so far, so most requests return empty_result, which is free. Costs 1 credit.

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

Input Schema

NameRequiredDescriptionDefault
urlYesReel, post or IGTV URL, or a bare shortcode
cache_max_ageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, openWorldHint), and the description adds substantial non-obvious behavior: the low likelihood of a result, that empty results are free, and that a hit costs 1 credit. That cost/likelihood disclosure is exactly the kind of context annotations cannot carry. It stops short of explaining auth or the cache behavior.

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 sentences, front-loaded with the resource, then provenance, then the practical warning about empty results and cost. Every sentence carries information; only minor trimming would be possible without losing signal.

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 usefully characterizes the return shape ('one text block plus timed cues') and the dominant empty-result case, which is enough for an agent to call it correctly. The one gap is the unexplained `cache_max_age` parameter, keeping it just under a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: `url` is documented in the schema, but `cache_max_age` has no description anywhere. The description adds nothing about either parameter — no input format hints beyond what the schema gives — so the undocumented parameter remains opaque to the agent.

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 opens with a specific resource (caption track for a Reel/video) and clarifies the data's origin — Instagram's published track, not an audio transcription. It is unmistakable what the tool returns, though it never contrasts itself with the transcript siblings (tiktok_transcript, youtube_transcript, facebook_postTranscript) that an agent may be choosing between.

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?

It provides useful decision context by warning that most requests yield `empty_result` and are free, which implies 'expect nothing'. However, there is no explicit when-to-use guidance relative to instagram_post, instagram_userReels, or the other transcript tools, leaving the agent to infer selection.

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.