Scribe

View saved version →

---
name: scribe
description: >-
  Create and manage Scribe email signatures, audit installs, read teammate and
  smart-field data, run marketing campaigns, and pull analytics through the
  Scribe MCP server. Use when the user wants to create, edit, preview, publish,
  or audit email signatures; manage reply and internal variants; add or look up
  teammates; read or set smart fields; organize folders or assets; run or report
  on marketing campaigns; or pull signature analytics, conversions, and visitors
  in Scribe.
---

# Scribe

Manage a Scribe workspace through the Scribe MCP server: signatures and their
reply and internal variants, teammates, smart fields, folders, assets,
integrations, marketing campaigns, analytics, and visitors.

## When to use this skill

Use it whenever the user wants to:

- create, edit, preview, publish, install, or audit email signatures
- add a reply or internal signature variant, or read the installed HTML
- assign signatures to teammates, org units, or rule-based audiences
- add, update, or look up teammates and their email aliases
- read or set smart fields (the merge fields that populate signatures)
- organize folders or upload assets (logos, banners, pictures)
- create, schedule, pause, or report on marketing campaigns
- pull signature analytics (views, clicks, conversions, revenue)
- look up identified visitors and where they came from

## Access

- Auth: OAuth sign-in as the user. Everything is scoped to the user's own
  workspace.
- Read tools run automatically. Write tools (create, update, delete, publish)
  ask the user for confirmation in the app.

## Core workflow: create a signature in the fewest calls

From a cold session, a complete signature takes three calls:

1. Call `get_content_schema` first. In one response it returns the strict
   block-tree schema, a flat lookup of every allowed enum value (including the
   non-obvious icon names such as `linkedin-in`, `facebook-f`), and a complete
   worked example with a populated social-icon row.
2. Adapt that example into a `draft_content` block tree and call
   `create_signature` with a `name` and the `draft_content`.
3. Call `publish_signature` to copy the draft into the live `content` and trigger
   installation.

To check the result before going live, call `preview_signature` on the draft and
read the returned HTML for layout and spacing, then publish.

Do not hand-write a block tree or guess enum spellings. Always call
`get_content_schema` before any `create_signature`, `update_signature`,
`update_signature_variant`, or marketing-campaign `content` write. An invalid
tree returns a 422 that names each offending field.

## Common patterns

- Audit installs: `list_signatures` (which templates are published and
  activated), then `list_signature_recipients` (who each one covers), then
  `list_integrations` (any failing connections).
- Verify a signature: `preview_signature` to check the draft layout before you
  publish, and `get_signature_html` to read what a specific recipient receives
  once it is live.
- Add a reply or internal variant: `get_content_schema`, then
  `update_signature_variant` to stage the variant draft, then
  `publish_signature_variant`. Variants need an active Microsoft 365 signatures
  integration.
- Look up teammate data: `list_teammates` (emails and smart-field values), with
  `list_smart_fields` for the field catalog.
- Fill gaps: read with `list_teammates`, then set values with `update_teammate`.
- Target a signature: `set_signature_recipient_rules` for auto-assign and
  conditions, `add_signature_recipients` for specific emails, or
  `add_signature_recipient_entities` for directory org units and groups.
- Run a campaign: `create_marketing_campaign`, then
  `schedule_marketing_campaign`.
- Report engagement: `get_analytics_views` and `get_analytics_clicks` for totals
  and a time series, or set `group_by` to rank signatures, teammates, campaigns,
  or countries. There is no clickthrough-rate field, so compute

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.