Skip to main content
Glama

job_transcribe

Transcribe an audio or video file (Whisper small)

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": {
      "media_url": "<media_url>"
    },
    "name": "job_transcribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
media_urlYespattern https://\S{4,2000}
max_resultsNodefault 10, at most 120

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It names the model but says nothing about supported formats, URL fetch requirements, latency, cost, or what a job submission returns; the agent cannot tell whether this is synchronous or queued.

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?

A single short sentence with no wasted wording and the core action front-loaded. It is efficient but arguably too terse for a job-submission tool.

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

Completeness2/5

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

With no annotations and no output schema, the description should explain the return shape (transcript text, job handle, status polling) and the meaning of max_results. None of that is present, leaving an agent uncertain how to consume the result.

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 both parameters are documented structurally, which sets the baseline at 3. The description adds no extra meaning, and notably does not explain why a transcription tool takes max_results, leaving that parameter's intent to the schema alone.

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 (transcribe) and resource (audio or video file) plus the underlying model (Whisper small), which is genuinely informative. It does not explicitly differentiate from the sibling job_transcribe_premium, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of alternatives, despite a clearly related sibling (job_transcribe_premium) existing. The only hint is the parenthetical model name, which the agent must infer implies a lower-quality/cheaper tier.

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.

Resources