Skip to main content
Glama

video_summarize

AI transcription + summary of an uploaded file — transcript included; 1 credit/min + 1. Costs 1 credit/min +1. 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_summarize"
  }
}

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 before summarizing. Default false.
timestampGranularityNosegment (default) or word.

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. Changed1 schema field 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."
  4. Changed3 schema fields changed
    • changedInput schema / properties / file / description
      Previous value: -"Local path to video/audio — 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."New value: +"ISO-639-1 Whisper language hint, e.g. \"en\" or \"tr\". Omit to auto-detect."
    • changedInput schema / properties / translate / description
      Previous value: -"Translate speech to English when true."New value: +"When true, translate speech to English before summarizing. 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 and summarize."New value: +"Local path to video/audio — multipart form field file (POST), not a query string."
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "ISO-639-1 Whisper language hint.",
      +  "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

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does add real behavioral context: per-minute credit pricing, a flat +1, no charge for empty results or failures, and fresh-vs-cached execution semantics. However, it instructs the agent to 'pass cache=true' while the input schema has no cache property and sets additionalProperties=false, so a key behavioral instruction is unusable and potentially misleading. Permissions/auth requirements and what the summary output looks like are also unstated.

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?

Front-loaded with the core purpose and the billing rule is useful, but the cost is stated twice in near-identical form ('1 credit/min + 1' then 'Costs 1 credit/min +1'), which is pure redundancy. The trailing cache sentence is the only forward-looking guidance and it points at a parameter that does not exist.

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 6-parameter, no-annotation, no-output-schema tool, the description covers cost and cache behavior but omits auth/permission needs and any indication of the summary's structure or length, which is the main thing an agent would want to know before spending credits. The dangling cache reference is an additional completeness defect.

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 six parameters (file, fields, compact, language, translate, timestampGranularity) are already fully documented, and the baseline is 3. The description adds nothing about any of them and instead references a nonexistent cache parameter, so it neither compensates nor reinforces the schema.

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 compound verb and resource: 'AI transcription + summary of an uploaded file', and clarifies that the transcript is included in the output. That distinguishes it implicitly from video_transcript and the platform-specific *_summarize siblings (which take URLs rather than uploads), but no sibling is named explicitly.

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 context is implied by 'uploaded file' (versus the URL-based summarize siblings) and by the caching note ('Pass cache=true for a free 24h cache hit'), which tells an agent when to opt into a cached run. There is no explicit when-to-use/when-not-to-use statement or named alternative such as video_transcript for transcript-only needs.

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.