Skip to main content
Glama
CamelMailer MCP Server

CamelMailer MCP Server

Official
by camelmailer

list_subscribers

Read-only

Retrieve the audience for a broadcast stream, including subscribed and unsubscribed addresses. Use this list to see who can receive sends, since unsubscribed addresses are refused.

Instructions

List a broadcast stream's subscribers, subscribed and unsubscribed alike. A broadcast send to an address that is not subscribed is refused, so this list is the audience.

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": {
      "permalink": "<permalink>"
    },
    "name": "list_subscribers"
  }
}

Input Schema

NameRequiredDescriptionDefault
permalinkYesBroadcast stream permalink

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds useful behavioral context: the list includes both subscribed and unsubscribed addresses, and it defines the broadcast audience. This goes beyond the safety hint without contradicting it.

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 concise sentences deliver the core purpose and the important audience implication without any wasted words. The main action is front-loaded.

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?

For a simple single-parameter read-only tool, the description provides enough information to select and call it correctly. It could mention the returned data shape, but the lack of an output schema is not a serious gap given the straightforward 'list' purpose.

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 schema has 100% parameter description coverage, with 'permalink' documented as 'Broadcast stream permalink.' The tool description does not need to add parameter details, so the baseline of 3 is appropriate.

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: 'List a broadcast stream's subscribers.' The phrase 'subscribed and unsubscribed alike' clarifies the exact scope and distinguishes this tool from subscriber-management siblings like add_subscriber and remove_subscriber.

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?

Provides clear usage context by explaining that non-subscribed addresses will be refused for broadcast sends, so this list represents the actual audience. It does not name explicit alternative tools or when-not-to-use conditions, but the intended use case is evident.

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