replyatlas-mcp

Send a broadcast

send_broadcast

Destructive

Preview and send a DRAFT broadcast to its audience: call once with broadcastId to see recipient counts, then confirm with a token to deliver it.

Instructions

Send a DRAFT broadcast to its audience. SAFETY: call once with {broadcastId} to preview the recipient counts and get a confirmToken; call again with the same broadcastId AND confirmToken to actually send. Requires the Pro plan.

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": {
      "broadcastId": "<broadcastId>"
    },
    "name": "send_broadcast"
  }
}

Input Schema

Name	Required	Description	Default
`broadcastId`	Yes
`confirmToken`	No	Echo the confirmToken from the preview to send.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already indicate this is not read-only and is destructive, but the description adds critical behavioral context: the two-step preview/confirm safety flow, recipient count preview, confirmToken issuance, and the Pro plan requirement. This is exactly the kind of extra operational detail annotations cannot convey.

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?

Three sentences, front-loaded with the purpose and immediately followed by the safety workflow. Every sentence earns its place and there is no redundant restatement.

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?

For a destructive, two-step send operation with no output schema, the description covers the essential workflow, safety requirement, and plan constraint. The preview output (recipient counts and confirmToken) is explained, and the final send action is unambiguous.

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?

With only 50% schema description coverage, the description carries more weight and explains both parameters in context: broadcastId selects the draft, and confirmToken from the preview is required to actually send. It does not explain the broadcastId pattern or all edge cases, but it substantially compensates for the schema gap.

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?

The description states a specific verb and resource: sending a DRAFT broadcast to its audience. It clearly distinguishes the tool from creation/listing siblings such as create_broadcast and list_broadcasts, and the two-phase preview/send workflow further sharpens its identity.

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?

It gives explicit operational guidance: call once for preview and a confirmToken, then call again with both to send. It also states the Pro plan requirement. It does not name alternative tools or when not to use this one, so it falls short of a full 5.

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