Scribe Mail

Target signature at org units

add_signature_recipient_entities

Idempotent

Target a signature at whole directory org units or groups (by uuid) so every teammate in them becomes a recipient. Use it to assign by team or department; use add_signature_recipients to assign individual emails, set_signature_recipient_rules for smart-field conditions, and remove_signature_recipient_entities to undo. Additive and idempotent: the uuids are merged into the existing org-unit targeting, and manual and condition-based recipients are kept. Membership is re-resolved after each directory sync, so people who later join a targeted unit get the signature too. Returns the full updated selection; unknown entity uuids fail with 422.

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."
`signature_id`	Yes	The signature template's UUID (the `id` from list_signatures).
`integration_entity_ids`	Yes	Org-unit/group uuids to add to the targeting: the `id` of each entity from list_integration_entities. At least one is required (an empty list returns 422); duplicates and already-targeted uuids are ignored.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026

changedInput schema / properties / integration_entity_ids / description

Previous value: -"Org-unit/group uuids to target (from list_integration_entities)."New value: +"Org-unit/group uuids to add to the targeting: the `id` of each entity from list_integration_entities. At least one is required (an empty list returns 422); duplicates and already-targeted uuids are ignored."

First observedOct 16, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond the annotations: discloses additivity, idempotent merge semantics, that manual and condition-based recipients are preserved, that membership is re-resolved after directory sync (future joiners inherit), and that unknown entity uuids fail with 422. The idempotent/read-only hints are merely confirmed rather than relied upon.

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?

Front-loads the core action and effect, then alternatives, then behavior, then failure mode. Every sentence carries distinct information with no padding.

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?

With an output schema present, return values need no explanation, and the description still covers mutation semantics, preservation of other recipient types, sync re-resolution, and the 422 failure path. Nothing material to a correct call is missing.

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 the baseline is 3; the description lifts this by explaining that uuids are merged into existing targeting, duplicates/already-targeted entries are effectively no-ops, and unknown uuids produce a 422. It does not restate param syntax, but it adds merge and failure semantics the schema only partially covers.

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 (target a signature) and resource (whole directory org units/groups by uuid), and immediately explains the effect: every teammate in them becomes a recipient. It explicitly distinguishes itself from add_signature_recipients and remove_signature_recipient_entities, so an agent can route correctly without opening either schema.

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?

Gives explicit when-to-use ('assign by team or department') and names the three alternative tools with the conditions that select each: individual emails, smart-field rules, and undo. This is a complete routing map for the recipient-targeting family.

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.