Skip to main content
Glama

list_recordings

Read-onlyIdempotent

List recent call recordings and their transcription status so you can identify which captured calls are ready or still need transcription.

Instructions

Latest recordings and their transcription state.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_recordings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description contributes only the word 'latest' (implying recency ordering) and 'transcription state' as a returned attribute; it says nothing about page size defaults, ordering stability, or whether transcription state is a snapshot.

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?

A single short sentence fragment with zero padding, so nothing is wasted. But at eleven words it is under-specified rather than concise: there is no room for the scope, ordering, or parameter context an agent needs.

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?

An output schema exists, so return shape need not be explained. Still, for a listing tool in a ten-sibling family with one undocumented parameter, the description omits ordering semantics, the limit default of 10, and any routing signal versus recording_status or get_transcript.

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?

The single parameter 'limit' has a default of 10 and 0% schema description coverage, so the description is the only place its meaning could be clarified — yet it is never mentioned. Nothing indicates whether limit caps rows, what the actual default ordering is, or what happens beyond the bound.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (recordings) and a distinguishing attribute (transcription state), which separates it from get_transcript and recording_status. However, it is a noun phrase with no verb, so it never explicitly says 'list' or describes the scope beyond 'latest', leaving the retrieval action implicit.

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 guidance, no exclusion, and no mention of any of the ten siblings. An agent cannot tell from this text whether to call list_recordings or recording_status to check a recording's state.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.