Skip to main content
Glama

list_broadcasts

Read-onlyIdempotent

Lists your account's broadcasts with public links, on-air status, listener counts, and current live transcription, filtered by active, archived, or all.

Instructions

List this account's broadcasts: live events listeners follow at a public link, reading (or hearing) what is said, translated into their own language as it is spoken; each listener picks from up to 10 languages, free, with no app or sign-up. For each: its link, whether it is on air, how many are listening, and the live transcription it is showing.

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_broadcasts"
  }
}

Input Schema

NameRequiredDescriptionDefault
lifecycleNoactive: in use; archived: in the trash; all: both.active

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful return context by naming link, on-air status, listener count, and displayed transcription, but it omits ordering, pagination, and how archived broadcasts are surfaced for the list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is front-loaded with a clear list action, but most of the sentence is product marketing about live events, translation, listener languages, and no sign-up. That material does not help an agent select or invoke this specific tool and crowds out operational details.

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?

For a simple, single-parameter read-only list tool, the description supplies the fields returned, which is useful because there is no output schema. However, it does not explain the lifecycle filter or result ordering/pagination, leaving operational gaps around the only parameter.

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 100%, and the single lifecycle enum is fully documented with active/archived/all. The description adds no additional meaning about how lifecycle affects results, so the schema is doing all the parameter work.

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 opening clause states a specific verb and resource: 'List this account's broadcasts.' That is clear, but the rest of the description spends most of its words explaining the broadcast product rather than distinguishing this list operation from the sibling get_broadcast or from filtered searches.

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 explicit guidance on when to use list_broadcasts rather than get_broadcast, search_transcriptions, or other siblings. The lifecycle parameter's active/archived/all distinction is only in the schema, not in the description.

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