Skip to main content
Glama

Agent Data Tools: Speech to text and text to speech

Summarize audio: voice note or meeting recording to summary and action items

transcribe_summary
Read-only

Summarize a voice note, meeting, call or podcast in one call: transcribes up to 60 minutes (MP3/WAV up to 25 MB; M4A, OGG or WebM up to 5 MB) by URL or upload, then returns a title, summary, key points, action items with owner and due date, open questions and the transcript, in the recording's language. Use for meeting notes, voicemail to CRM and call notes. Example: url=https://upload.wikimedia.org/wikipedia/commons/7/77/Tofino_pronunciation.mp3. Price $0.05/call via x402 USDC or a card key (/credits); failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http(s) URL of the recording (MP3/WAV up to 25 MB and 60 minutes; M4A, OGG or WebM up to 5 MB); or POST the file itself (raw body, multipart `file` part, or base64 in JSON)
languageNoSpoken language code such as en, sv or de (default: detected)
transcriptNofalse: leave the full transcript out of the answer (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: cost ($0.05/call via x402 USDC or card key at /credits), failed calls free, every call charged so repeats are not free (reinforcing idempotentHint=false), and the explicit 'reads or computes only and changes nothing' statement matching readOnlyHint=true. Media constraints and language-of-output behavior are also disclosed.

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 with the core purpose and output list, followed by audience, a concrete example URL, then pricing and safety notes. Dense but each sentence carries information; the price/payment sentence is the most compressed and slightly busy but still earns its place given the per-call charge.

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

Completeness5/5

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

With no output schema, the description fully enumerates the return payload and its language behavior, plus cost, limits and side-effect profile. An agent can decide to call it, know what it will get back, and understand the billing consequence without opening anything else.

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 documents url, language and transcript. The description adds the output-language default behavior but never mentions the transcript=false toggle, so it contributes little meaning the schema does not already carry; 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?

States a specific verb and resource ('Summarize a voice note, meeting, call or podcast in one call') and enumerates the exact outputs: title, summary, key points, action items, open questions, transcript. It implicitly separates itself from plain transcription siblings via 'transcribes ... then returns', but it never names transcribe, transcribe_long, or ai_summarize, so the differentiation is left for the agent to infer.

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?

Gives concrete use cases ('meeting notes, voicemail to CRM and call notes') and hard boundaries (60 minutes, 25 MB for MP3/WAV, 5 MB for M4A/OGG/WebM), which effectively route oversized inputs elsewhere. It stops short of naming an alternative tool or an explicit when-not-to-use condition.

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.