Skip to main content
Glama

video_transcript

AI transcription of an uploaded file — 1 credit/min; noSpeech=true and 0 credits when there is no speech. Costs 1 credit/min. Empty results and failures are never charged. Pass cache=true for a free 24h cache hit (default always fresh).

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": {
      "file": "<file>"
    },
    "name": "video_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesVideo or audio file (multipart form field — use -F file=@path, not a query string). Max 200MB / 60 minutes.
fieldsNoOptional comma-separated keys to keep on each result row (or on the object for single-item tools), e.g. id,url,publishedAt,engagement. Pagination keys are always kept. Does not change the price.
compactNoDefault true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. On Threads, Facebook, Meta Ad Library and TikTok Shop tools request timings are dropped too. Pass false for the full body.
languageNoISO-639-1 language hint, e.g. "en" or "tr". Omit to auto-detect.
translateNoWhen true, translate speech to English. Default false.
timestampGranularityNosegment (default) or word — word-level timings when the transcription model exposes them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / compact / description
      Previous value: -"Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. Pass false for the full body."New value: +"Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. On Threads, Facebook, Meta Ad Library and TikTok Shop tools request timings are dropped too. Pass false for the full body."
  2. Changed2 schema fields changed
    • addedInput schema / properties / compact
      Added value: +{
      +  "default": true,
      +  "description": "Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. Pass false for the full body.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / fields
      Added value: +{
      +  "description": "Optional comma-separated keys to keep on each result row (or on the object for single-item tools), e.g. id,url,publishedAt,engagement. Pagination keys are always kept. Does not change the price.",
      +  "type": "string"
      +}
  3. Changed3 schema fields changed
    • changedInput schema / properties / language / description
      Previous value: -"ISO-639-1 Whisper language hint, e.g. \"en\" or \"tr\". Omit to auto-detect."New value: +"ISO-639-1 language hint, e.g. \"en\" or \"tr\". Omit to auto-detect."
    • changedInput schema / properties / timestampGranularity / description
      Previous value: -"segment (default) or word — word-level timings when Whisper exposes them."New value: +"segment (default) or word — word-level timings when the transcription model exposes them."
    • changedInput schema / properties / translate / description
      Previous value: -"When true, translate speech to English (Whisper translations API). Default false."New value: +"When true, translate speech to English. Default false."
  4. Changed4 schema fields changed
    • changedInput schema / properties / file / description
      Previous value: -"Local path to video/audio — sent as multipart form field file (POST), not a query string."New value: +"Video or audio file (multipart form field — use -F file=@path, not a query string). Max 200MB / 60 minutes."
    • changedInput schema / properties / language / description
      Previous value: -"ISO-639-1 Whisper language hint, e.g. en or tr."New value: +"ISO-639-1 Whisper language hint, e.g. \"en\" or \"tr\". Omit to auto-detect."
    • changedInput schema / properties / timestampGranularity / description
      Previous value: -"segment (default) or word."New value: +"segment (default) or word — word-level timings when Whisper exposes them."
    • changedInput schema / properties / translate / description
      Previous value: -"Translate speech to English when true."New value: +"When true, translate speech to English (Whisper translations API). Default false."
  5. Changed4 schema fields changed
    • changedInput schema / properties / file / description
      Previous value: -"Local path or multipart file upload of the video/audio to transcribe."New value: +"Local path to video/audio — sent as multipart form field file (POST), not a query string."
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "ISO-639-1 Whisper language hint, e.g. en or tr.",
      +  "type": "string"
      +}
    • addedInput schema / properties / timestampGranularity
      Added value: +{
      +  "description": "segment (default) or word.",
      +  "type": "string"
      +}
    • addedInput schema / properties / translate
      Added value: +{
      +  "description": "Translate speech to English when true.",
      +  "type": "boolean"
      +}
  6. Added

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does disclose pricing (1 credit/min), the no-speech outcome (noSpeech=true, 0 credits), and that failures are never charged, which is genuinely useful. However, it introduces a 'cache' parameter that does not exist in the schema (additionalProperties: false), which is actively misleading, and it says nothing about output shape, permissions, or async/latency behavior.

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

Conciseness3/5

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

Short and front-loaded, but the cost is stated twice ('1 credit/min' and 'Costs 1 credit/min'), and the parenthetical cache note is buried at the end where it reads as an afterthought. Tightening would free space for the missing output and alternative-tool guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter transcription tool with no annotations and no output schema, the description covers billing and the no-speech edge case but omits what the response actually contains (transcript text, segments, timings) and how the timestampGranularity/translate options shape it. The dangling 'cache' reference further undercuts completeness.

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 coverage is 100%, so the schema already documents all six parameters, and the description adds no meaning for file, language, translate, timestampGranularity, fields, or compact. Worse, it references a 'cache' flag that is absent from the schema, so an agent following the description would attempt an invalid argument.

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: 'AI transcription of an uploaded file'. The word 'uploaded' implicitly separates it from the many URL-based transcript siblings (youtube_transcript, tiktok_transcript), but the description never names an alternative, so the differentiation is left to inference.

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?

Usage is only implied by 'uploaded file' — there is no explicit when-to-use or when-not-to-use guidance versus the platform-specific transcript tools. The cache advice ('Pass cache=true for a free 24h cache hit') is parameter guidance rather than tool-selection guidance.

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.