Scribe Mail

Update a signature variant

update_signature_variant

DestructiveIdempotent

Create or update a signature's reply/internal variant (upsert). Passing draft_content or activated: true creates the variant if it doesn't exist yet. draft_content stages the variant's working copy — publish_signature_variant copies it live. Also toggles activated (use a distinct variant vs. the primary), hidden (show no signature on this kind of email), and show_marketing_campaigns. Only the fields you pass change (omit = leave as-is; draft_content: null clears it). When editing draft_content, call get_content_schema first. Variants require an active Microsoft 365 signatures integration — otherwise 409 variants_unavailable.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	Yes	Which variant: reply (reply emails) or internal (same-domain emails).
`hidden`	No	Hide any signature on this kind of email.
`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."
`activated`	No	Use a distinct variant on this kind of email (creates it if needed).
`signature_id`	Yes	The primary signature's UUID (the `id` from list_signatures).
`draft_content`	No	Variant draft block tree (ILayoutBlock): a `stack` root whose `children` are blocks. Strict-validated server-side. Setting it creates the variant if needed. Omit to leave unchanged; null to clear. Every node (block AND token) needs an `id` that is a fresh LOWERCASE uuid — any other string, including an uppercase uuid, is rejected 422. Every numeric size is in PIXELS, never a CSS multiplier: `lineHeight` is a px line box (~1.3x fontSize, e.g. fontSize 14 -> 18), so 1.3 is rejected. Call get_content_schema for the full schema, every enum value, and a worked example.
`show_marketing_campaigns`	No	Append marketing campaigns on this kind of email.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare destructive/idempotent/openWorld, and the description layers on upsert semantics, partial-update behavior ('only the fields you pass change'), the null-clears rule, the staging-vs-live model, and a concrete failure mode (409 variants_unavailable). This is disclosure well beyond the structured hints.

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?

Purpose leads, then creation triggers, then the toggles, then the editing rule and error case. Every sentence conveys a distinct behavioral fact with no filler, appropriate for a complex 7-parameter upsert.

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 not be described. The description covers creation conditions, partial-update semantics, clearing, the sibling to call for live publishing, the schema-discovery prerequisite, and the hard integration requirement, leaving no operational gap for the agent.

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 nonetheless adds real meaning by framing draft_content as a staged working copy, stating that null clears it and omission leaves it unchanged, and directing to get_content_schema. This is more than restating the schema, though the schema already carries most per-field detail.

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 ('Create or update a signature's reply/internal variant (upsert)') and scopes it to the reply/internal kinds. An agent can immediately distinguish it from publish_signature_variant, delete_signature_variant, and list_signature_variants without opening any 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?

Explicitly names the alternatives and the conditions that select them: 'publish_signature_variant copies it live' and 'When editing draft_content, call get_content_schema first.' It also gives the prerequisite (active Microsoft 365 signatures integration, else 409 variants_unavailable) and the creation triggers.

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.