Skip to main content
Glama

captapi

by io.github.CDCStream

instagram_transcript

Turn any Instagram Reel's speech into text — the full transcript plus timestamped segments, ready for search, subtitles, or AI pipelines. Costs 2 credits. Empty results and failures are never charged. Pass cache=true for a free 24h cache hit (default always fresh).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesInstagram Reel URL, e.g. https://instagram.com/reel/ID/. The URL platform must match this endpoint's platform. Do not pass cross-platform URLs, e.g. YouTube to TikTok, Instagram to Facebook, LinkedIn to X/Twitter, or Pinterest to Rumble.
cacheNoSet true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh.
languageNoPreferred caption language as an ISO code, e.g. "en". Defaults to auto-detect.

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden. It adds meaningful operational context: the 2-credit cost, no charge for empty results or failures, and the cache=true free cache-hit behavior with a default fresh fetch. This gives an agent a realistic picture of cost and side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two compact sentences with no filler. The core purpose is front-loaded, followed by essential cost and cache policy. Every sentence earns its place.

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 or annotations, so the description must explain both output and behavior. It covers the transcript output, timestamped segments, cost, failure billing, and cache semantics. Missing an explicit alternative-tool routing note, but the clear platform scope makes the definition sufficiently complete for a straightforward transcription tool.

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%, so the schema already fully documents all three parameters, including the URL platform-match warning, cache behavior, and language ISO default. The description reinforces cache behavior but adds no significant new parameter-level meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Turn speech into text'), a specific resource ('Instagram Reel's speech'), and specifies the output ('full transcript plus timestamped segments'). This clearly distinguishes the tool from sibling transcript tools for YouTube, TikTok, LinkedIn, and other platforms.

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

Usage Guidelines4/5

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

The Instagram Reel scope makes the intended use case explicit and unambiguous. It does not explicitly name alternative transcript tools or state when not to use them, but the platform constraint is clear enough for an agent to select the correct tool.

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

All captapi toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation3/5

The platform-prefix convention keeps most of the 178 tools clearly separated, but several clusters are genuinely ambiguous: tiktok_live_info is explicitly described as 'Identical to TikTok Live', instagram_basic_profile and instagram_channel_details both return profile stats, and facebook_profile_posts overlaps with facebook_profile_reels. The generic 'Summarizer' descriptions for facebook_summarize, instagram_summarize, and tiktok_summarize provide no disambiguating detail at all.

Naming Consistency4/5

The dominant snake_case platform_resource_suffix pattern is followed remarkably consistently across 178 tools (e.g. youtube_channel_videos, tiktok_search_users, reddit_subreddit_posts). Minor deviations exist: the same creator resource is called 'channel' in some tools (tiktok_channel_details, instagram_channel_posts) but 'profile' or 'user' in others (facebook_profile_posts, twitch_user_videos, linnkme_profile); link-in-bio tools mostly use _page but linkme uses _profile; and the video_summarize/video_transcript pair lacks a platform prefix.

Tool Count2/5

At 178 tools this is far beyond what any agent can efficiently navigate in a single flat namespace, and even individual platform subsets exceed reasonable bounds (TikTok alone has ~34 tools, YouTube ~25). The sheer breadth of the multi-platform scope partially justifies the count, but the server would be far more usable split into per-platform servers.

Completeness4/5

The read-only data surface is impressively thorough: nearly every platform has profile + content + search + comments coverage, and TikTok, YouTube, Instagram, and Facebook are covered end-to-end including shops, ads, transcripts, and summaries. Notable gaps are minor: Twitter has no keyword search tool, LinkedIn lacks comments, and Reddit has no user-profile endpoint, but none of these create dead ends for the server's core data-retrieval purpose.

Resources