GoodSender

List Recipients

list_recipients

Read-onlyIdempotent

List recipients with group memberships and their last known consent status per verified sender domain (as of ConsentStateAsOf).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_recipients"
  }
}

Input Schema

Name	Required	Description	Default
`Limit`	No	Max recipients (default 500, capped at 1000).
`AfterEmail`	No	Pagination: return recipients with email strictly after this string (empty = first page).

Output Schema

Name	Required	Description	Default
`Recipients`	Yes	Recipients in email order.
`ConsentStateAsOf`	No	When consent state was last refreshed from GoodSender; absent when not yet refreshed in this server session. This tool does not refresh it.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 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 readOnly, idempotent, non-destructive, closed-world. The description adds genuinely non-obvious semantics: consent status is a snapshot 'as of ConsentStateAsOf' and is scoped to verified sender domains only, which changes how an agent should interpret results. It stays silent on pagination behavior, but the schema covers that.

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?

One front-loaded sentence with no filler; every clause (group memberships, consent status, sender-domain scope, as-of semantics) carries information an agent needs.

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?

An output schema exists so return shape needn't be explained, and parameters plus safety hints are already structured. The only real gap is usage/routing guidance, otherwise the definition is complete enough to invoke correctly.

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% — Limit (default 500, cap 1000) and AfterEmail pagination are fully explained in the schema. The description adds nothing about either parameter, so the baseline 3 applies.

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?

Specific verb + resource (list recipients) plus the two payload facets it returns: group memberships and per-sender-domain consent status. This clearly separates it from list_groups and list_sender_identities, though it never names a sibling explicitly.

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?

There is no statement of when to use this versus alternatives (edit_recipient, delete_recipients, list_groups), nor any mention of when paging is needed. The use case is only implied by the verb 'List'.

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

All GoodSender 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.