> ## Documentation Index
> Fetch the complete documentation index at: https://help.scribe-mail.com/llms.txt
> Use this file to discover all available pages before exploring further.

> Design render-safe, on-brand Scribe email signatures. Use when the user wants to build, restyle, or fix the layout of a signature, add a logo or banner, set up social icons, preview rendering, manage reply or internal variants, or organize templates into folders. Always reads the content schema before writing content.

# Scribe signature design

# Scribe signature design

Build valid, render-safe signature layouts through the Scribe MCP server.

## When to use

* Create a signature from a brief, an example, or a screenshot
* Restyle an existing signature or fix layout and spacing
* Add a logo, banner, or social-icon row
* Match a brand's colors, fonts, and structure
* Preview rendering before publishing, or read a recipient's installed HTML
* Add a reply or internal variant of a signature
* Organize templates into folders

## Workflow

1. Call `get_content_schema` first. It returns the block-tree schema, every
   allowed enum value (including icon names like `linkedin-in`, `facebook-f`),
   and a worked example. Never hand-write a tree or guess enum spellings.
2. Adapt the example into `draft_content` and call `create_signature` or
   `update_signature`.
3. Call `preview_signature` and read the returned HTML to check layout and
   spacing while it is still a draft.
4. Call `publish_signature` to make it live, or `install_signature` to install
   the current live content without publishing.

## Variants

A variant is an alternate signature shown on reply emails or on internal
(same-domain) emails. Call `get_content_schema`, stage the variant with
`update_signature_variant`, then `publish_signature_variant`. Variants need an
active Microsoft 365 signatures integration; without it, variant writes return a
409 `variants_unavailable`.

## Tool reference

Access key: Read runs automatically, Write asks for confirmation, Delete is
destructive.

| Tool                        | Access | What it does                                                                                        |
| --------------------------- | ------ | --------------------------------------------------------------------------------------------------- |
| `get_content_schema`        | Read   | Returns the block-tree schema, all enum values, and a worked example. Call before authoring content |
| `list_signatures`           | Read   | List signature templates                                                                            |
| `create_signature`          | Write  | Create a template, staged as draft until you publish                                                |
| `update_signature`          | Write  | Update a template, staged as draft until you publish                                                |
| `preview_signature`         | Read   | Render a draft or published template to HTML with placeholder values to check layout                |
| `get_signature_html`        | Read   | Get the real installed HTML of a published signature for a specific recipient                       |
| `publish_signature`         | Write  | Publish so the draft becomes live and installs                                                      |
| `install_signature`         | Write  | Install the current live content without publishing                                                 |
| `delete_signature`          | Delete | Delete a template and unassign it                                                                   |
| `list_signature_variants`   | Read   | List a signature's reply and internal variants                                                      |
| `update_signature_variant`  | Write  | Create or update a reply or internal variant, staged as a draft                                     |
| `publish_signature_variant` | Write  | Publish a variant so its draft becomes live                                                         |
| `delete_signature_variant`  | Delete | Reset a variant back to the primary signature                                                       |
| `list_folders`              | Read   | List signature folders with counts                                                                  |
| `create_folder`             | Write  | Create a folder to organize templates                                                               |
| `update_folder`             | Write  | Rename a folder                                                                                     |
| `delete_folder`             | Delete | Delete a folder (must be empty first)                                                               |
| `list_assets`               | Read   | List the image library (logos, banners, pictures)                                                   |
| `create_asset`              | Write  | Upload an image from base64 or a source URL                                                         |
| `update_asset`              | Write  | Update an asset's name or role                                                                      |
| `delete_asset`              | Delete | Delete an asset (in-use assets are soft-deleted)                                                    |

## Rendering notes

* Keep layouts table-based and inline-styled so they hold up in Outlook, Gmail,
  and Apple Mail.
* `preview_signature` shows placeholder values and needs no recipient, so use it
  to verify a draft. `get_signature_html` returns the real installed HTML for one
  recipient and is empty until the signature is published.
* An invalid tree returns a 422 that names each offending field. Fix and retry.