mcp

list_broadcast_recipients

Read-only

Who a campaign reached and what happened to each message, with the A/B variant when there is one. At most 200 per call; while has_more is true, next_cursor (a message id) passed back as cursor returns the next page.

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": {
      "id": "<id>"
    },
    "name": "list_broadcast_recipients"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The campaign's id from create_broadcast or list_broadcasts (a UUID), not its name
`limit`	No	Page size, 1 to 200; defaults to 200
`cursor`	No	next_cursor from the previous page, passed back unchanged

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 15, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "next_cursor from the previous page, passed back unchanged",
+  "type": "string"
+}

addedInput schema / properties / id / description

Added value: +"The campaign's id from create_broadcast or list_broadcasts (a UUID), not its name"

addedInput schema / properties / limit / description

Added value: +"Page size, 1 to 200; defaults to 200"

changedInput schema / properties / limit / maximum
```
Previous value: -1000New value: +200
```

First observedSep 2, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond them: a hard 200-per-call cap, the has_more/next_cursor pagination contract, and the fact that next_cursor is a message id passed back as cursor.

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?

Two tight sentences, front-loaded with what is returned and followed by the pagination mechanics. No filler and nothing that fails to earn its place.

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?

With no output schema, the description usefully sketches the return shape (recipients, per-message outcomes, A/B variant) and fully covers the pagination loop. Only minor gaps remain, such as failure behavior for an unknown campaign id or ordering of results.

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%, so all three parameters are already documented, which sets the baseline at 3. The description restates the limit and cursor round-trip but adds no format or edge-case detail the schema lacks.

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?

States a specific resource and scope: recipients of a campaign plus per-message outcomes and the A/B variant. That distinguishes it from list_broadcasts and get_broadcast without needing the schema, though the verb 'list' is only implied rather than stated.

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?

The description explains the pagination loop but never says when to reach for this tool versus get_broadcast or get_email_metrics, and gives no prerequisites or exclusions. The only routing hint (where the id comes from) lives in the schema, not the description.

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

All mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.