Skip to main content
Glama

TranscriptLab

List transcript library

transcriptlab_list_transcripts
Read-onlyIdempotent

List YouTube videos whose transcripts were already delivered to this account, most recent first. Use it to find or reopen an earlier transcript. It fetches nothing and delivers no transcript. When more results exist, page with the returned cursor.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size; defaults to the server default.
cursorNoOpaque cursor returned by the previous page.
searchNoOptional video ID or title filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), so the description earns credit for adding non-obvious behavior: account/locale scoping, most-recent-first ordering, and cursor-based paging. The explicit negative guarantee that no transcript is delivered is valuable disambiguation not present in any structured field. It stops short of describing the returned record fields, which matters with no output schema.

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?

Four short sentences, front-loaded with the resource and ordering, then the use case, then the key negative constraint, then paging. Nothing is filler; the only mild overlap is between "use it to find or reopen" and "delivers no transcript," which reads as intentional boundary-setting rather than waste.

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?

For a three-param, read-only listing tool with full schema coverage and no output schema, the definition covers purpose, scope, ordering, and paging. The remaining gap is the shape of each returned list item (video ID, title, delivery timestamp), which the agent must discover empirically. That is a minor omission rather than a blocking one.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3 and the schema carries parameter definitions. The description goes beyond it by explaining the paging contract ("When more results exist, page with the returned cursor"), clarifying the cursor's role in a workflow rather than just its type. Limit default and search filter semantics are left entirely to the schema.

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

Purpose5/5

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

Specific verb and resource ("List YouTube videos whose transcripts were already delivered to this account") plus result ordering (most recent first) and account scoping. It actively distinguishes itself from transcript-retrieval siblings by stating "It fetches nothing and delivers no transcript," so an agent can rule out transcriptlab_get_transcript and peers without opening schemas.

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 clear use case ("find or reopen an earlier transcript") and a clear non-use (it does not fetch transcript content), which effectively routes the agent to the retrieve tools for the actual content. It does not name a specific sibling as the follow-up step, and "reopen" slightly overstates what this call alone accomplishes, keeping it below a 5.

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.