Skip to main content
Glama

List Magic Reach Message Recipients

list_magic_reach_message_recipients
Read-only

List recipients for one Magic Reach message. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

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": {
      "communityId": "<communityId>",
      "messageId": "<messageId>"
    },
    "name": "list_magic_reach_message_recipients"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNoPage number to return, starting at 1.
filtersNo
pageSizeNoNumber of results per page.
platformNoMessaging channel; use one of the allowed values.
messageIdYesMagic Reach message ID.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
messageTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
    • addedInput schema / properties / messageId / description
      Added value: +"Magic Reach message ID."
    • addedInput schema / properties / pageNo / description
      Added value: +"Page number to return, starting at 1."
    • addedInput schema / properties / pageSize / description
      Added value: +"Number of results per page."
    • addedInput schema / properties / platform / description
      Added value: +"Messaging channel; use one of the allowed values."
  2. First observed

TDQS

B3.3/5.0
Behavior4/5

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

The annotations already declare a safe read (readOnlyHint true, destructiveHint false), so the lower bar applies, and the description still adds real behavioral context: FREE businesses are excluded regardless of feature rows, a business-permission check is mandatory, and grace-period warnings and a verified resubscribe link must be surfaced before continuing. That is meaningful authorization and gating behavior beyond the annotations. It does not cover pagination behavior or what the recipient records contain, which keeps it below a 5.

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

Conciseness3/5

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

Purpose is front-loaded in the first sentence, which is good, but the remaining three sentences are repetitive permission boilerplate: the check_business_tool_access prerequisite is stated three separate ways ('check business permissions', 'Call check_business_tool_access', 'never proceed when access is blocked'). The permission messaging could be compressed to one sentence, freeing space for the parameter guidance that is currently missing.

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 read-only paginated listing tool with no output schema and a nested filters object, the description covers the access-control dimension thoroughly but leaves the actual listing behavior opaque — no indication of return shape, paging conventions, or how filters/messageType affect results. An agent could gate access correctly from this text but would have to open the schema to learn how to page or filter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description says nothing about any of the 7 parameters — no explanation of filters, platform, messageType, or paging behavior. With schema coverage at 71%, the schema documents pageNo, pageSize, platform, messageId, and communityId, but 'filters' (a nested object) and 'messageType' are undocumented in both places, and the description does not compensate at all.

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 first sentence names a specific verb and resource with clear scope: 'List recipients for one Magic Reach message.' An agent can distinguish this from count_magic_reach_recipients or export_magic_reach_message_recipients_csv by intent, though the description never actually says which sibling to use when the agent wants filtering or totals. It is clear but not sibling-differentiating.

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

Usage Guidelines3/5

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

There is strong guidance on prerequisites ('Call check_business_tool_access before collecting inputs', 'never proceed when access is blocked'), but that is access gating rather than tool-selection guidance. The description never mentions when to prefer search_magic_reach_recipients over this list, or how this differs from count_magic_reach_recipients, so alternative selection is left to inference.

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.

Resources