Skip to main content
Glama

List broadcasts

list_broadcasts
Read-onlyIdempotent

Use this when the founder wants to see a project's email broadcasts, to pick up a draft they started, or to find one a follow-up should build on. They come newest first: drafts, scheduled, sending, sent. Each row has the bcd_… handle, name, status, subject, when it was scheduled or sent, and the headline results (recipients, delivered, bounced, unsubscribed). Filter by status (draft, scheduled, sending, sent, paused, canceled, failed) to narrow it. Not for one broadcast's content or recipients (use get_broadcast).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>"
    },
    "name": "list_broadcasts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return, 1-50. Defaults to 20.
statusNoOnly broadcasts in this status.
projectYesThe project handle, like `prj_…`.
starting_afterNoA `bcd_…` handle from the previous page, to continue after it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes further by disclosing result ordering ('newest first: drafts, scheduled, sending, sent') and the exact per-row payload (bcd_ handle, name, status, subject, dates, headline metrics). That is context an agent could not derive from the annotations or schema.

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?

Front-loaded with the usage decision and then the return shape, so the most decision-relevant sentence comes first. The opening 'when the founder wants to…' framing and the redundant status enumeration add some length that could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, but the description compensates by enumerating the row fields and the ordering, which is exactly what an agent needs to use the results. Filtering and pagination are covered between the description and the fully documented schema.

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 coverage is 100%, so the schema already documents limit, status, project and starting_after; the description only restates the status filter and actually omits the `queuing` value present in the schema enum, a small inconsistency. Pagination and limit 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?

States a specific verb and resource ('see a project's email broadcasts') and immediately scopes it against the sibling: 'Not for one broadcast's content or recipients (use get_broadcast)'. An agent can distinguish list_broadcasts from get_broadcast without opening either schema.

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

Usage Guidelines5/5

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

Gives concrete when-to-use triggers (pick up a draft, find one a follow-up should build on) and an explicit when-not-to-use with the named alternative. The only minor gap is that other list_* siblings are not contrasted, but the primary ambiguity is resolved.

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.