Skip to main content
Glama

Get call recording

get_recording
Read-only

Temporary playable recording URL for a call you own. The URL expires; do not treat it as a permanent link. Offer it after summarizing the result; do not lead with the recording.

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": {
      "call_id": "<call_id>"
    },
    "name": "get_recording"
  }
}

Input Schema

NameRequiredDescriptionDefault
call_idYesCall id to get a temporary playable recording URL for.

Output Schema

NameRequiredDescriptionDefault
recording_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive, non-openWorld, so the safety profile is covered; the description adds genuinely new behavioral facts: the URL is temporary, expires, and must not be cached as a permanent link. That expiry caveat is the key operational risk an agent needs and is not present in any structured field.

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?

Three short sentences, each doing distinct work: what the resource is, the expiry caveat, and the interaction ordering rule. The most actionable constraint (temporary URL) is front-loaded with no filler.

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?

An output schema exists and annotations cover safety, so the description need not explain returns. It covers expiry and presentation, the two things an agent would otherwise get wrong. It omits what happens on an unauthorized or invalid call_id, a minor gap for a single-parameter read.

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?

Only one parameter and schema coverage is 100%, with the schema already describing call_id as the id to get a temporary recording URL for. The description adds the ownership constraint on that id, which is a small but real increment beyond the schema, so baseline 3 is right.

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+resource (retrieve a temporary playable recording URL) and scopes it to 'a call you own,' which implicitly separates it from transcript or metadata siblings. It does not explicitly name an alternative tool, so the differentiation is inferred from the resource noun rather than stated.

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 a concrete presentation rule: offer the URL only after summarizing the result and never lead with it. The ownership precondition ('a call you own') also frames when this is valid. It stops short of naming alternatives such as get_call_transcript for agents that actually want text rather than audio.

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.