Scribe Mail

List a signature's recipients

list_signature_recipients

Read-onlyIdempotent

REQUIRES signature_id (a signature template UUID) — there is no workspace-wide form of this tool. Without one in hand, call list_signatures first and pass an id from it. List the emails a signature is assigned to — each with the sources explaining why (manual, smart_field, or an org unit) — plus the selection config (manual ids, targeted org units, smart-field conditions, and the assign-to-all-future flag). data is paginated; selection is the full rule config.

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": {
      "signature_id": "<signature_id>",
      "context": "<context>"
    },
    "name": "list_signature_recipients"
  }
}

Input Schema

Name	Required	Description
`page`	No	1-based page (default 1).
`limit`	No	Page size, 1–100 (default 50).
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`max_pages`	No	Page cap when auto_paginate is true (default 5).
`signature_id`	Yes	The signature template's UUID (the `id` from list_signatures).
`auto_paginate`	No	Fetch multiple pages up to `max_pages` (default false).

Output Schema

Name	Required	Description
`data`	Yes
`selection`	Yes
`truncated`	Yes	True when auto_paginate stopped at max_pages with more results remaining.
`pagination`	Yes
`pages_fetched`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 28, 2026
- removedOutput schema / properties / data / items / properties / sources / items / properties / integration_entity_id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / sources / items / properties / integration_entity_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedOct 16, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description still adds useful behavior: `data` is paginated while `selection` returns the complete rule config unpaginated, and it enumerates the `sources` values (manual, smart_field, org unit). It stops short of explaining default page size or the auto_paginate interaction, which the schema covers.

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

Conciseness4/5

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

Front-loads the blocking requirement in the first clause, then describes the return shape, with no filler sentences. Dense em-dash construction makes it slightly harder to scan but every clause carries information.

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 the description need not explain return values, yet it usefully summarizes them. With annotations covering the safety profile and the schema covering pagination knobs, the only minor omission is edge behavior (e.g. a signature with zero recipients).

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?

Schema coverage is 100%, so baseline is 3, but the description earns a bump by clarifying the pagination scoping: page/limit apply to `data` only, not to the `selection` object. It also restates the origin of `signature_id`, which duplicates the schema rather than extending it.

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 the emails a signature is assigned to') and names exactly what the response contains (emails with `sources`, plus `selection` rule config). It also forecloses confusion with a sibling by declaring there is no workspace-wide variant, so an agent can tell it apart from list_signatures and list_signature_installations.

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?

Explicitly states the prerequisite (`signature_id`) and gives a concrete fallback: call list_signatures first and pass an `id` from it. That is real routing guidance, but it does not address closely related write operations (add/remove_signature_recipients, set_signature_recipient_rules) that an agent might confuse this read with.

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

All Scribe Mail 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.