Skip to main content
Glama
Sign In
assemblyai-mcp

assemblyai-mcp

by karpovantonme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_transcripts

Fetch recent transcripts from your account, using status and limit filters to narrow results for review or management.

Instructions

List recent transcripts on the account.

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
limitNoHow many to return. Default 20
statusNoOnly return transcripts in this status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the burden. 'List recent transcripts' conveys a read-only, account-scoped, recency-ordered operation, but it does not explicitly state non-mutation, pagination behavior, or what fields the returned transcripts contain. This is minimal but not misleading.

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?

The description is one short, front-loaded sentence with no filler. The only slight weakness is the undefined term 'recent,' but structurally it is appropriately concise.

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?

The tool is simple and has full parameter documentation, so the description is minimally adequate for invocation. However, with no output schema and no annotations, the return format/fields and precise ordering semantics are left unspecified.

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?

The input schema fully documents both parameters, including default and maximum for limit and the status enum, so the baseline 3 applies. The description adds no parameter-level meaning beyond what the schema already provides.

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 names a specific operation ('List') and resource ('transcripts'), and narrows scope to 'recent' and 'on the account.' It is clear at a glance and distinguishable from the singular get_transcript or search_transcript, though it does not explicitly name those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use this tool: when the agent needs a list of recent account transcripts. It does not mention alternatives such as search_transcript or get_transcript, nor does it state when not to use it, so the usage guidance is only implicit.

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

Deploy Server

Other Tools