Skip to main content
Glama

List transcripts

list_transcripts
Read-onlyIdempotent

Lists a bounded page of transcripts in the connected Wisprs tenant, filterable by status, folder, and deleted 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_transcripts"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
statusNo
folderIdNo
pageSizeNo
includeDeletedNo

Output Schema

NameRequiredDescriptionDefault
itemsYes
nextStepNo
nextCursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / nextStep
      Added value: +{
      +  "maxLength": 240,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observed

TDQS

B3.3/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 behavior, so the safety profile is covered. The description adds useful context that results are a 'bounded page' in a specific tenant, but it does not explain ordering, cursor semantics, or rate limits beyond that.

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?

A single front-loaded sentence with no wasted words; the verb and resource come first and the filter scope follows immediately.

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?

With an output schema present, return values need not be explained, and annotations cover safety. However, for a paginated list tool with five parameters and zero schema descriptions, the omission of cursor and pageSize guidance leaves a meaningful gap for correct invocation.

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 0%, so the description must carry parameter meaning. It maps three of five parameters conceptually ('status, folder, and deleted state'), but cursor and pageSize receive no explanation and no defaults, formats, or enum semantics are added.

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?

The description states a specific verb and resource ('Lists a bounded page of transcripts') plus tenant scope and filter dimensions, so an agent can distinguish it from get_transcript or export_transcript. It stops short of explicitly naming a sibling alternative for filtered versus unfiltered listing.

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?

It implies the tool is for browsing transcripts filtered by status, folder, or deleted state, but gives no explicit when-to-use versus when-not guidance and never points to alternatives such as get_transcript for a single record. The agent must infer usage from the purpose statement alone.

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.