Scribe Mail

Add manual signature recipients

add_signature_recipients

Idempotent

Manually assign a signature to specific email addresses (by email uuid). Use it to add named people one by one; use add_signature_recipient_entities to target whole org units or groups, set_signature_recipient_rules for smart-field conditions or all future emails, and remove_signature_recipients to undo. Additive and idempotent: the emails join the manual list, and org-unit and condition-based recipients are kept. When the signature's installation is on and a signature integration can push it, Scribe queues installation on its recipients' mailboxes right away. Returns the full updated selection; check who it reaches with list_signature_recipients. Needs the signatures:write scope; an unknown signature returns 404.

Input Schema

TableJSON Schema

Name	Required	Description
`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."
`email_ids`	Yes	Email uuids to assign as manual recipients: the `id` from list_emails (or a teammate's `emails[].id` from list_teammates), not teammate ids. At least one is required (an empty list returns 422); if any uuid is unknown the whole batch fails with 422 and nothing is added. Duplicates and already-assigned emails are ignored.
`signature_id`	Yes	The signature template's UUID (the `id` from list_signatures).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

changedInput schema / properties / email_ids / description

Previous value: -"Email uuids to assign as manual recipients (re-adding an existing one is a no-op)."New value: +"Email uuids to assign as manual recipients: the `id` from list_emails (or a teammate's `emails[].id` from list_teammates), not teammate ids. At least one is required (an empty list returns 422); if any uuid is unknown the whole batch fails with 422 and nothing is added. Duplicates and already-assigned emails are ignored."

First observedOct 16, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations (idempotentHint, destructiveHint, readOnlyHint), the description discloses the additive semantics (org-unit and condition-based recipients preserved), the side effect that Scribe queues installation on recipients' mailboxes immediately, the 404 for unknown signatures, and the required signatures:write scope.

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?

Dense but front-loaded: the manual-assignment purpose leads, sibling routing and behavioral notes follow. Every clause carries information, though the routing and behavior sentences are somewhat packed together.

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 mutation tool with an output schema present, the description covers the essentials an agent needs: additive/idempotent behavior, install side effect, error code, scope, and confirmation path via list_signature_recipients. Return format needn't be described since the output schema exists.

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 coverage is 100% and the schema already explains uuid sources, batch-failure (422), and duplicate handling in depth. The description only restates "by email uuid", adding little beyond the schema, so the baseline 3 applies.

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 ("Manually assign a signature to specific email addresses (by email uuid)") and immediately contrasts with add_signature_recipient_entities for org units, so an agent can distinguish it from siblings without opening schemas.

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

Usage Guidelines5/5

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

Explicitly routes: "use add_signature_recipient_entities to target whole org units or groups, set_signature_recipient_rules for smart-field conditions or all future emails, and remove_signature_recipients to undo." The when/when-not and alternatives are all named.

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.