Instadata — Instagram Data API

Get a video transcript

get_transcript

Read-onlyIdempotent

Spoken-word transcript of a public video, with timestamped segments where the source publishes them. Instagram only. Credits: 1 per call plus 20 per started minute of video. Input: url.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Full public URL of the post, video, profile or page.

Output Schema

Name	Required	Description
`data`	Yes	The endpoint's payload: one object, or an array for list calls.
`meta`	No	count, limit and next_cursor on list calls; credits_charged, credits_remaining and cache (hit or miss) on billed calls; limit_clamped when fewer items were requested upstream than the balance could cover; limit_capped when a free account's request was lowered to the free tier's 5-item ceiling.
`request_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds substantive context beyond that: the credit pricing model (1 + 20 per started minute) and the conditional caveat that timestamps only exist "where the source publishes them" — both directly affect whether an agent should invoke it. It stops short of noting failure modes or whether a video without a transcript still burns credits.

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 and dense: scope, availability caveat, platform, and cost all land in three short sentences. The trailing "Input: url." earns nothing and could be dropped.

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?

An output schema exists, so return values need no explanation, and the description covers the genuinely non-obvious facts: platform scope and per-minute cost. What remains thin is edge-case behavior — unavailability of timestamps is flagged, but no-transcript handling and credit consumption on failure are unstated.

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 coverage, the schema already documents the URL fully. "Input: url." merely restates it and adds no constraint, format, or platform-URL nuance beyond what the schema provides, so baseline 3 applies.

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?

"Spoken-word transcript of a public video" gives a specific verb+resource, and "Instagram only" narrows the domain. It is clearly distinguishable from siblings like download_media or get_post_stats, though it never explicitly contrasts with get_summary, which could also return text derived from a video.

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 platform exclusion ("Instagram only") tells the agent when not to call it, which is more than most definitions offer. However, no alternative is named for non-Instagram URLs, and there is no guidance on transcript vs. summary selection despite get_summary being a sibling.

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

All Instadata — Instagram Data API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?