Scribe Mail
Server Details
Email signature management finally simple and measurable. Built for teams & AI agents. Install consistent signatures company-wide in under a day. IT sets up once. Marketing takes over. AI agents assist. No employee installation. 12% average CTR on signature banners. Conversion tracking from click to revenue.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- scribemail/claude-plugin
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- Scribe Mail
TDQS
Scored across 69 tools
Despite 69 tools, descriptions actively disambiguate near-neighbours: add_signature_recipients vs add_signature_recipient_entities vs set_signature_recipient_rules, preview_signature vs get_signature_html vs send_test_email, and install_signature vs install_signature_for_email each state explicitly when to use which. The weakest zone is analytics, where get_analytics_views, get_analytics_clicks, get_analytics_events_summary, list_analytics_events and get_visitor_breakdown return similar breakdown shapes and an agent must reason about intent rather than resource. Residual confusion is possible but mostly resolved by the descriptions themselves.
Uniform snake_case verb_noun throughout: list_/get_/create_/update_/delete_/preview_/publish_/install_ + resource. Families are predictable (list_signatures/list_folders/list_teammates/list_assets; create_/update_/delete_ mirrored across signatures, folders, smart_fields, marketing_campaigns). Minor outliers like get_more_tools or create_first_signature still follow the pattern rather than breaking it.
69 tools is far past the point where an agent can hold the surface in view, and the rubric's 25+ threshold applies. The domain is genuinely broad (signatures, variants, folders, smart fields, teammates, emails, assets, campaigns, analytics, visitors, integrations, docs, billing, feedback), which explains but does not excuse the size; several tools (get_more_tools, create_first_signature, duplicate_signature, send_feedback, list_financial_documents) are peripheral to the core signature-deployment job.
Lifecycle coverage is strong: signatures have create/update/duplicate/publish/preview/install/delete plus recipient and variant management, and folders, smart fields, teammates, emails, assets and campaigns all have near-full CRUD with activation/state transitions. Gaps are minor and explicitly acknowledged (no single-signature or single-campaign get, no address search, no workspace-wide recipient listing), all workable via list calls, so no true dead ends.
Publisher details
- Operator
- Scribe SAS · Publisher source
- Operator website
- https://www.scribe-mail.com · Publisher source
- Vendor relationship
- First-party · Publisher source
- Documentation
- https://help.scribe-mail.com/en/ai-agents · Publisher source
- Privacy policy
- Not provided
- Trust center
- https://security.scribe-mail.com · Publisher source
- Restrictions
- Requires a Scribe workspace on a Business or Enterprise plan, or an active 14-day trial; the Free plan has no API access. The signed-in user must be a workspace owner or admin. · Publisher source
Available Tools
69 toolsadd_signature_recipient_entitiesTarget signature at org unitsAIdempotentInspect
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.
Inputs: context (required), signature_id (required), integration_entity_ids (required). Returns: data
add_signature_recipientsAdd manual signature recipientsAIdempotentInspect
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.
Inputs: context (required), email_ids (required), signature_id (required). Returns: data
create_assetCreate an assetAInspect
Upload an image to the workspace's asset library. Provide EITHER file_base64 (+ filename) OR source_url — exactly one. For a file the user uploaded in chat (no public URL), send its bytes as file_base64; if you cannot read the raw bytes on this platform, ask the user for a hosted URL or reuse an existing asset from list_assets instead of guessing. Non-images, bad base64, oversized files (>15MB), or a disallowed URL return 422.
Inputs: context (required), name, role, filename, +2 more. Returns: data
create_emailCreate an emailAInspect
Add an alias email address to a teammate. Only available when the workspace manages its own team list — if a directory integration (Google, Microsoft or Zoho Mail) drives teammates, this returns a 409 conflict. The address is validated (format, uniqueness, disposable/deny-list) → 422 on failure.
Inputs: address (required), context (required), teammate_id (required). Returns: data
create_first_signatureStart the first signature from the company's brandAInspect
Start a workspace's first email signature the way Scribe's web onboarding does: it looks up the company behind the user's email domain (name, logo, brand color and style, button labels, social links, phone, address, the person's name and job title) and builds the onboarding's template that suits the brand, saved as a DRAFT and returned rendered so you can show it. Use it right after create_scribe_account, or for a workspace that has no signature yet. Never publishes: publish_signature only after the person approves.
Inputs: context (required), create_another. Returns: data, signature, next_steps
create_folderCreate a folderAInspect
Create a new, empty signature folder to organize signature templates. Folders created here are top-level (not nested). Use it only when no suitable folder exists: call list_folders first to reuse one, and use update_folder to rename an existing folder instead of creating another, since duplicate names are allowed. Creating a folder files nothing: to put a signature in it, pass the returned id as folder_id to create_signature or update_signature. Writes one folder and returns it with signature_count 0. Needs the folders:write scope; a blank name returns 422.
Inputs: name (required), context (required). Returns: data
create_marketing_campaignCreate a marketing campaignAInspect
Create a marketing campaign. name, start_time, end_time, and time_zone are required; a missing one returns 422. The campaign is created as a draft — use schedule_marketing_campaign to activate it. content is a block tree (a stack root whose children are blocks) strict-validated server-side, the same format as signature draft_content; smart_fields_conditions and signature_template_ids set the targeting.
Inputs: name (required), context (required), end_time (required), time_zone (required), +7 more. Returns: data
create_scribe_accountCreate a Scribe accountAInspect
Create the Scribe account of the person signed in to this connector, when they have none yet (other Scribe tools say so). Creates their workspace with a free 14-day trial, from the email they signed in with, which must be a company address. ONLY call it after: (1) the person said they do NOT already have a Scribe account (someone who has one must reconnect with their Scribe email instead, or they get a second, empty workspace); (2) you showed them the Terms and Conditions (https://www.scribe-mail.com/terms-and-conditions) and the Privacy Policy (https://www.scribe-mail.com/privacy-policy); and (3) they explicitly agreed to create the account. Pass accept_terms: true only then.
Inputs: context (required), accept_terms (required), time_zone. Returns: data, next_steps
create_signatureCreate a signatureAInspect
Create a signature template. Sets draft_content (the working copy) — content stays empty until you publish_signature. name is required; draft_content is a block tree (a stack root whose children are blocks) strict-validated server-side; folder_id is a folder UUID. Call get_content_schema FIRST for the block-tree schema, every enum value (incl. the non-obvious icon names like linkedin-in/facebook-f), and a complete worked example to adapt — that's how you build a full signature, social-icon row included, in one shot. An invalid tree returns 422 naming each offending field and (for enums) its allowed values. Returns the created template.
Inputs: name (required), context (required), priority, folder_id, +2 more. Returns: data
create_smart_fieldCreate a smart fieldAInspect
Define a new custom smart field, a merge field signature templates and campaign conditions can use. Check list_smart_fields first: labels are unique, and to rename, retype or rebind an existing field use update_smart_field instead. A manual field starts empty; set each teammate's value with update_teammate. Bound to an integration (integration_id + integration_attribute), its values come from that integration and update_teammate can no longer set them; integrations do not fill url fields, so keep a url field manual. Creating the field changes no signature until a template references it. Writes one field and returns it. Needs the smart_fields:write scope; a taken label, an invalid kind or an unknown or unsuitable integration returns 422.
Inputs: label (required), context (required), kind, required, +2 more. Returns: data
create_teammateCreate a teammateAInspect
Create a new teammate from a primary email plus optional smart-field values. Only available when the workspace manages its own team list — if a directory integration (Google, Microsoft or Zoho Mail) drives teammates, this returns a 409 conflict. Email aliases are managed separately.
Inputs: email (required), context (required), smart_fields. Returns: data
delete_assetDelete an assetADestructiveIdempotentInspect
Delete an asset by UUID. If it's still in use (referenced by a signature or set as the workspace picture) it is soft-deleted so those keep rendering; otherwise it is permanently removed. Either way it disappears from list_assets.
Inputs: id (required), context (required). Returns: id, deleted
delete_emailDelete an emailADestructiveIdempotentInspect
Delete an alias email by UUID (soft delete). A teammate's primary email cannot be deleted (returns 422). Only available when the workspace manages its own team list — a directory integration returns a 409 conflict.
Inputs: id (required), context (required). Returns: id, deleted
delete_folderDelete a folderADestructiveIdempotentInspect
Delete a signature folder by UUID. A folder that still contains signatures cannot be deleted (returns 409) — move or delete its signatures first.
Inputs: id (required), context (required). Returns: id, deleted
delete_marketing_campaignDelete a marketing campaignADestructiveIdempotentInspect
Delete a marketing campaign by UUID. An active campaign is stopped first (it stops applying to signatures), then removed.
Inputs: id (required), context (required). Returns: id, deleted
delete_signatureDelete a signatureADestructiveIdempotentInspect
Permanently delete a signature template by UUID; there is no undo or trash. The template is removed with its recipient assignment (manual, org-unit and smart-field rules), its marketing-campaign targeting and its installation records, but Scribe does not push an uninstall to mailboxes it was already installed in. Use it only when the template itself should go: to stop it reaching some people, use remove_signature_recipients or remove_signature_recipient_entities; to reset only a reply or internal variant, use delete_signature_variant. Needs the signatures:delete scope; an unknown id returns 404.
Inputs: id (required), context (required). Returns: id, deleted
delete_signature_variantReset a signature variantADestructiveIdempotentInspect
Reset a signature's reply/internal variant back to the primary: deactivate it and restore the primary's content (the variant record is kept). This is the 'reset to primary' action, not a hard delete. Returns 409 if the workspace lacks a Microsoft 365 signatures integration (variants_unavailable).
Inputs: kind (required), context (required), signature_id (required). Returns: kind, reset, signature_id
delete_smart_fieldDelete a smart fieldADestructiveIdempotentInspect
Delete a custom smart field by UUID (this also removes its value on every teammate). Default fields are read-only (422), the computed Email field is not addressable (404), and a field used in a signature template or campaign can't be deleted (409).
Inputs: id (required), context (required). Returns: id, deleted
delete_teammateDelete a teammateADestructiveIdempotentInspect
Delete a teammate by UUID (a soft delete; their emails are removed from signature deployment). Only available when the workspace manages its own team list — if a directory integration (Google, Microsoft or Zoho Mail) drives teammates, this returns a 409 conflict.
Inputs: id (required), context (required). Returns: id, deleted
duplicate_signatureDuplicate a signatureAInspect
Copy a signature into a new one, as the dashboard's Duplicate: a safe copy to try a change on (a new banner, a layout) without touching the original or anyone's signature. The copy gets the source's design (its draft, published as the copy's content) and its reply/internal variants; it is assigned to no one, its installation is off, it has no smart-field rules. Use it instead of reading the design and create_signature. Then edit the copy with update_signature and check it with preview_signature; to bring a tried change back, update_signature the original with the copy's draft_content. Unknown signature → 404; unknown folder → 422. Returns the copy.
Inputs: id (required), context (required), name, folder_id. Returns: data
get_analytics_clicksAnalytics — signature clicksARead-onlyIdempotentInspect
Signature-click counts over a date range. By DEFAULT a timeseries bucketed by granularity (hour/day/week/month, UTC): { data:[{period, count}], totals:{count} }. Set group_by (signature_template | marketing_campaign | teammate | country) for a ranked breakdown instead: { data:[{id, label, view_count, click_count, clickthrough_rate}], pagination } — each breakdown row already carries views, clicks, AND the clickthrough rate, so one call answers "which signature/teammate drives the most engagement". Filter by start_date/end_date and any of signature_template_id, marketing_campaign_id, teammate_id.
Inputs: context (required), page, limit, order, +7 more. Returns: result
get_analytics_events_summaryAnalytics — conversions & revenue (aggregated events)ARead-onlyIdempotentInspect
Aggregated conversion/revenue numbers from recorded events. By DEFAULT a timeseries of event count + sum of value bucketed by granularity: { data:[{period, count, value}], totals:{count, value} }. Set group_by (name | signature_template | marketing_campaign | teammate | anchor | country | currency | user) for a ranked breakdown: { data:[{id, label, count, value}], pagination } — rank by order_by (count | value). value is summed across currencies, so pass currency or group_by=currency for a clean total. Answers total revenue, revenue by campaign/template/teammate/country, conversions per day, top customers (group_by=user).
Inputs: context (required), name, page, limit, +12 more. Returns: result
get_analytics_viewsAnalytics — signature viewsARead-onlyIdempotentInspect
Signature-view counts over a date range. By DEFAULT a timeseries bucketed by granularity (hour/day/week/month, UTC): { data:[{period, count}], totals:{count} }. Set group_by (signature_template | marketing_campaign | teammate | country) for a ranked breakdown instead: { data:[{id, label, view_count, click_count, clickthrough_rate}], pagination } — each breakdown row already carries views, clicks, AND the clickthrough rate, so one call answers "which signature/teammate drives the most engagement". Filter by start_date/end_date and any of signature_template_id, marketing_campaign_id, teammate_id.
Inputs: context (required), page, limit, order, +7 more. Returns: result
get_content_schemaGet the content schemaARead-onlyIdempotentInspect
Call this FIRST before authoring or editing a signature draft_content (create_signature / update_signature) or a marketing-campaign content. Returns, in ONE call, everything needed to build a valid block tree: the strict JSON Schema; a flat enums lookup of every allowed value (including the 100+ valid icon names and the iconStyle.shape values); the social_icons map from common platform to its exact (non-obvious) icon enum, e.g. linkedin -> linkedin-in, facebook -> facebook-f, youtube -> youtube, instagram -> instagram, whatsapp -> whatsapp; a complete worked example signature containing every block type AND a populated 5-platform socialList; and short guidance. Adapt example to author a full signature — social-icon row included — without guessing the format or brute-forcing enum spellings.
Inputs: context (required). Returns: data
get_more_toolsARead-onlyIdempotentInspect
Check for additional tools whenever your task might benefit from specialized capabilities - even if existing tools could work as a fallback.
Inputs: context (required).
get_signature_htmlGet a signature's real HTML for a recipientARead-onlyIdempotentInspect
Get the REAL final installed HTML of a signature for a SPECIFIC recipient — the live published content rendered with that teammate's real values and tracking links on, i.e. exactly what their mail client receives. This is NOT a preview: it reflects the published signature (publish_signature first), and returns empty HTML if the signature has not been published. The email must be a recipient of this signature (see list_signature_recipients), otherwise the API returns a 404 (no such email) or 422 (not a recipient). For a tracking-free placeholder layout check of a draft before publishing, use preview_signature instead.
Inputs: id (required), context (required), email_id (required). Returns: data
get_visitorGet a visitorARead-onlyIdempotentInspect
Fetch one identified visitor (the customer's identify subject — NOT a Scribe member) by its Scribe id — the uuid from list_visitors, not the distinct_id (to look up by distinct_id, filter list_visitors instead). Returns the visitor's distinct_id, traits (PII lives here), first/last_seen_at, first_touch attribution (the signature click that drove their first visit), and stats — the visitor's lifetime engagement (event count + total value).
Inputs: id (required), context (required). Returns: data, stats
get_visitor_breakdownVisitor acquisition breakdown (first-touch)ARead-onlyIdempotentInspect
Rank which signature template or teammate acquired the most identified visitors (the first signature click that drove their first visit): { data:[{id, label, count}], pagination }.
Inputs: context (required), group_by (required), page, limit. Returns: data, pagination
get_workspaceWorkspace plan, seats & tracking setupARead-onlyIdempotentInspect
A snapshot of the current workspace's commercial state: plan (tier, kind, status, billing_interval, cancel_at_period_end + start/end dates), seat_count (invoiced seats — what Stripe is billed for), and event_tracking (conversion-tracking setup: the Event Tracking ID to paste into the website snippet / @scribemail/js init, plus whether events would be ingested). When helping a user set up conversion tracking, read the ID here and search_docs for 'conversion tracking' to walk them through the snippet, identify() and track() calls. There is no id — it is always the API key's own workspace. Read-only: plan and seats are managed in the dashboard / by the billing system, never via the API.
Inputs: context (required). Returns: data
install_signatureInstall a signatureADestructiveInspect
Trigger installation of a signature template's current content to connected mail clients (without publishing), on every email it is assigned to; for one email alone, use install_signature_for_email. Returns 403 if the plan lacks signature installation, or 409 if no API signature integration is connected — in both cases the error includes a dashboard link to connect an integration or upgrade the plan; relay it to the user (the API can't run OAuth).
Inputs: id (required), context (required). Returns: data
install_signature_for_emailInstall the signatures of one emailADestructiveInspect
Install one email's signatures now, in its mailbox alone, without reinstalling the signature for everyone else (install_signature): a send-as alias that needs its signature, one person whose details changed (a new title). Installs the installed (activated) and published signatures assigned to the email, or only signature_id, through the workspace's signature integrations (Google Workspace, Zoho Mail, Front, …). Runs in the background: the result lists what was queued, and list_signature_installations with the email_id shows each one as it ends. 409 installed_by_client when the Outlook add-in or the desktop app installs the workspace's signatures: the client picks up the latest published signature by itself, there is nothing to push, say so. 409 no_signature_to_install when no installed signature is assigned to the email; 422 not_a_recipient when signature_id is not assigned to it. Returns 403 if the plan lacks signature installation, or 409 installation_unavailable if no signature integration is connected; relay the dashboard link.
Inputs: context (required), email_id (required), signature_id. Returns: data
list_analytics_eventsList analytics eventsARead-onlyIdempotentInspect
List the raw conversion events recorded for the workspace (from the website SDK and server-to-server calls), most recent first, one row per event with its attribution uuids and its properties returned as recorded. Use it to verify that conversion tracking works, to read one visitor's event history (distinct_id) or to export rows. For counts, revenue or rankings use get_analytics_events_summary instead, which aggregates; for signature views and clicks use get_analytics_views / get_analytics_clicks; for visitor profiles use list_visitors. Events are ingested asynchronously, so one tracked seconds ago may not show yet. Read-only; needs the analytics:read scope and a plan with event tracking (403 otherwise). Returns one page (default 50, max 100); set auto_paginate to fetch up to max_pages, and truncated: true means more remain.
Inputs: context (required), name, page, limit, +9 more. Returns: data, truncated, pagination, pages_fetched
list_assetsList assetsARead-onlyIdempotentInspect
List the workspace's asset library (logos, banners, profile pictures), newest first. Each has its id, a downloadable file URL, its role, in_use (a signature or the workspace picture references it) and signature_template_count. Use it to reuse an image: put an asset's id in an image block's assetUuid (see get_content_schema) rather than uploading a duplicate with create_asset. Also use it to find the id for update_asset or delete_asset, and check in_use first, since delete_asset only soft-deletes an asset in use. Deleted assets are excluded and there is no filter by role, so page through and match role or name. Read-only; needs the assets:read scope. Returns one page (default 50, max 100); set auto_paginate to fetch up to max_pages, and truncated: true means more remain.
Inputs: context (required), page, limit, max_pages, +1 more. Returns: data, truncated, pagination, pages_fetched
list_emailsList emailsARead-onlyIdempotentInspect
List the workspace's teammate email addresses, primary and aliases, newest first, each with its id, address, primary flag and owning teammate_id. Use it to get the email id that add_signature_recipients, remove_signature_recipients, update_email, delete_email, install_signature_for_email and send_test_email take. Use list_teammates instead when you also need smart-field values: it embeds each teammate's emails too. There is no address search: filter by teammate_id, or page through and match address. Deleted emails and teammates are excluded. Read-only; needs the emails:read scope. Returns one page (default 50, max 100); set auto_paginate to fetch up to max_pages, and truncated: true means more remain.
Inputs: context (required), page, limit, max_pages, +2 more. Returns: data, truncated, pagination, pages_fetched
list_financial_documentsList financial documentsARead-onlyIdempotentInspect
List the workspace's financial documents (invoices and credit notes), newest first. Only documents with a downloadable PDF are returned: each carries a file ({ url, filename, content_type, byte_size }) whose url downloads the document, plus a receipt (same shape) when a separate receipt PDF exists. Use the file.url to fetch/download the document. Read-only — documents are issued by the billing system, not via the API. Paginated (page/limit).
Inputs: context (required), page, limit, max_pages, +1 more. Returns: data, truncated, pagination, pages_fetched
list_foldersList foldersARead-onlyIdempotentInspect
List the workspace's signature folders, newest first, each with its id, name and signature_count (the signature templates it directly contains). Use it to find a folder id for update_folder, delete_folder or the folder_id of create_signature / update_signature, and to check for an existing folder before create_folder, since names need not be unique. It does not list the signatures inside a folder: use list_signatures and match each one's folder_id. A folder whose signature_count is above 0 cannot be deleted (delete_folder returns 409). Asset folders are not included. Read-only; needs the folders:read scope. Returns one page (default 50, max 100); set auto_paginate to fetch up to max_pages, and truncated: true means more remain.
Inputs: context (required), page, limit, max_pages, +1 more. Returns: data, truncated, pagination, pages_fetched
list_integration_entitiesList integration entitiesARead-onlyIdempotentInspect
List the workspace's directory org units / groups (from a teammates integration). Their uuids are what you pass to add_signature_recipient_entities to target a signature at a whole org unit. Paginated (page/limit).
Inputs: context (required), page, limit, max_pages, +1 more. Returns: data, truncated, pagination, pages_fetched
list_integrationsList active integrationsARead-onlyIdempotentInspect
List the workspace's active (set-up) integrations, including any currently failing. Each carries a status ("active" or "error") and, when erroring, an error_message + error_since so you can see which integrations are connected and debug what went wrong. Each also has a dashboard_url to manage or reconnect it — relay that link when an integration is in error (the API can't run OAuth). Integrations are connected and configured in the dashboard, not via the API — and connecting one (Google Workspace, Microsoft 365, Zoho Mail, …) must be done by a SUPER ADMIN of that third-party app (an Admin is enough in Zoho Mail), so guide the user rather than trying to act: use search_docs (e.g. 'connect Microsoft 365', 'Google Workspace setup') to fetch the step-by-step setup guide and walk them through it alongside the dashboard link. This is WORKSPACE-level health only — for per-email install state/errors (e.g. a recipient not found on Front) use list_signature_installations. Paginated (page/limit).
Inputs: context (required), page, limit, max_pages, +1 more. Returns: data, truncated, pagination, pages_fetched
list_marketing_campaignsList marketing campaignsARead-onlyIdempotentInspect
List the workspace's marketing campaigns (signature banners), each with its status, schedule, targeting and content block tree. Use it to find a campaign's id before update_, schedule_, pause_, resume_, delete_ or preview_marketing_campaign; there is no single-campaign get and no server-side filter, so pick the campaign from this list. To see the rendered banner rather than its block tree, use preview_marketing_campaign. Read-only. Returns one page by default; set auto_paginate to fetch up to max_pages pages in one call, and truncated: true means more remain, so call again with a later page.
Inputs: context (required), page, limit, max_pages, +1 more. Returns: data, truncated, pagination, pages_fetched
list_signature_installationsList per-email signature installation stateARead-onlyIdempotentInspect
Where each signature actually IS (or failed to be) installed, per email: one row per email × signature × integration/email client with status (installed | failed | uninstalled) and, on failure, the error_code (e.g. user_not_found = the recipient has no account on that integration). Use this to answer 'is X's signature installed on ?' or 'which installs failed and why?' — list_integrations only reports workspace-level connection health. Filter by email_id or email_address, signature_template_id, integration_id, status.
Inputs: context (required), page, limit, status, +6 more. Returns: data, truncated, pagination, pages_fetched
list_signature_recipientsList a signature's recipientsARead-onlyIdempotentInspect
REQUIRES signature_id (a signature template UUID) — there is no workspace-wide form of this tool. Without one in hand, call list_signatures first and pass an id from it. List the emails a signature is assigned to — each with the sources explaining why (manual, smart_field, or an org unit) — plus the selection config (manual ids, targeted org units, smart-field conditions, and the assign-to-all-future flag). data is paginated; selection is the full rule config.
Inputs: context (required), signature_id (required), page, limit, +2 more. Returns: data, selection, truncated, pagination, +1 more
list_signaturesList signaturesARead-onlyIdempotentInspect
List the workspace's email-signature templates. A Scribe 'signature' is a reusable template (the layout that gets deployed to teammates' mail clients); v1 returns the workspace's primary templates. Paginated (page/limit). The large content/draft_content block trees are omitted by default — pass include_content:true to fetch them.
Inputs: context (required), page, limit, max_pages, +2 more. Returns: data, truncated, pagination, pages_fetched
list_signature_variantsList signature variantsARead-onlyIdempotentInspect
List a signature's reply and internal variants (always both entries). A variant is an alternate signature shown on reply emails (reply) or internal/same-domain emails (internal). Each entry reports its state (exists / activated / hidden / show_marketing_campaigns) and content. Also returns supported: variants require an active Microsoft 365 signatures integration, and writes return 409 variants_unavailable when it's false.
Inputs: context (required), signature_id (required). Returns: data, supported
list_smart_fieldsList smart fieldsARead-onlyIdempotentInspect
List the workspace's smart-field definitions — the merge fields available to signature templates (e.g. first name, job position, custom fields). Each carries its kind, whether it's a default field, and an integration_id when its values are synced. The computed Email field is not exposed. Paginated (page/limit).
Inputs: context (required), page, limit, max_pages, +1 more. Returns: data, truncated, pagination, pages_fetched
list_teammatesList teammatesBRead-onlyIdempotentInspect
List the workspace's teammates. A 'teammate' is a managed person whose email signature Scribe deploys; each carries their email addresses and smart-field values (the data merged into signature templates). Paginated (page/limit).
Inputs: context (required), page, limit, max_pages, +1 more. Returns: data, truncated, pagination, pages_fetched
list_visitorsList identified visitorsARead-onlyIdempotentInspect
The workspace's identified visitors — the customer's own end-users, described by their identify calls (NOT Scribe members/teammates). Each row: distinct_id, traits (PII lives here), first/last_seen_at, and first_touch (the signature click that drove their first visit). Filter by distinct_id (exact), a trait (trait_key + trait_value, e.g. plan=enterprise), identified_via, and first-seen date range. Newest first, paginated.
Inputs: context (required), page, limit, end_date, +7 more. Returns: data, truncated, pagination, pages_fetched
pause_marketing_campaignPause a marketing campaignAInspect
Pause an active campaign — it stops applying to signatures. Only an active campaign can be paused (otherwise 409). Resume later with resume_marketing_campaign.
Inputs: id (required), context (required). Returns: data
preview_marketing_campaignPreview a campaign (placeholder values)ARead-onlyIdempotentInspect
Render a marketing campaign's content block tree to HTML with PLACEHOLDER values — the same recipient-less, tracking-free render preview_signature does. Use it to VERIFY a banner's layout after create/update_marketing_campaign and BEFORE schedule_marketing_campaign: read the returned html, confirm it looks right, fix the content if not. An empty html means the campaign has no content yet.
Inputs: id (required), context (required). Returns: data
preview_signaturePreview a signature (placeholder values)ARead-onlyIdempotentInspect
Render a signature to HTML with PLACEHOLDER values (each smart field shows its label, like the editor canvas for an empty field) — no recipient needed. Use this to VERIFY layout and spacing after create_signature / update_signature and BEFORE publish_signature: read the returned html to confirm the result looks right (no overlapping lines, correct spacing), and fix the draft if not. Renders the draft by default; pass content:"published" for the live copy.
Inputs: id (required), context (required), content. Returns: data
publish_signaturePublish a signatureADestructiveInspect
Publish a signature template: copy draft_content into the live content and, when the workspace can, trigger installation to connected mail clients. SIDE EFFECT: a successful publish also activates installation for the template (signature_installation_activated becomes true) — the signature goes live to its recipients' mail clients, not just in the API. Confirm with the user before publishing a signature that has recipients. Returns the updated template (with last_published_at set).
Inputs: id (required), context (required). Returns: data
publish_signature_variantPublish a signature variantADestructiveInspect
Publish a signature's reply/internal variant: copy its draft_content into the live content and redeploy through the primary signature. Returns the updated variant (with last_published_at set). Returns 409 if the variant hasn't been created yet (variant_not_created) or if the workspace lacks a Microsoft 365 signatures integration (variants_unavailable).
Inputs: kind (required), context (required), signature_id (required). Returns: data
read_docs_pageRead a help-center pageARead-onlyIdempotentInspect
Fetch the FULL content of one Scribe help-center page by its path (from a search_docs result). Use it when the search excerpt isn't enough — e.g. to walk a user step-by-step through an integration setup, DNS configuration, or the conversion-tracking install. Public documentation; needs no scope and touches no workspace data.
Inputs: path (required), context (required). Returns: path, content
remove_signature_recipient_entitiesUntarget signature from org unitsADestructiveIdempotentInspect
Stop targeting a signature at a batch of directory org units / groups (by uuid). Manual and condition-based recipients are untouched. Returns the updated selection.
Inputs: context (required), signature_id (required), integration_entity_ids (required). Returns: data
remove_signature_recipientsRemove manual signature recipientsADestructiveIdempotentInspect
Remove a batch of manual recipients (by email uuid) from a signature. Only manual assignment is affected — emails matched by a condition or org unit stay. Returns the updated selection.
Inputs: context (required), email_ids (required), signature_id (required). Returns: data
resume_marketing_campaignResume a marketing campaignAInspect
Resume a paused campaign — it becomes active again. Only a paused campaign with a future end time can be resumed (otherwise 409). Returns 403 if the workspace's plan does not include marketing campaigns.
Inputs: id (required), context (required). Returns: data
schedule_marketing_campaignSchedule a marketing campaignAInspect
Launch a draft or paused marketing campaign on its own dates. If the campaign's start_time (set with create_ or update_marketing_campaign) has passed, it goes live at once and the targeted signatures Scribe pushes are reinstalled with the banner; otherwise its status becomes scheduled and it starts at start_time. Use it to launch a draft from create_marketing_campaign, after checking the banner with preview_marketing_campaign. To restart a paused campaign now, use resume_marketing_campaign, which ignores start_time; to stop one, pause_marketing_campaign; to change dates, update_marketing_campaign first. Not idempotent: a campaign that is not draft or paused, or whose end_time has passed, returns 409. Needs the marketing_campaigns:write scope; 403 if the plan lacks marketing campaigns.
Inputs: id (required), context (required). Returns: data
search_docsSearch the Scribe help centerARead-onlyIdempotentInspect
Search the official Scribe help-center documentation (help.scribe-mail.com) and return matching excerpts with titles and links. ALWAYS use this before answering product/how-to questions from memory — how smart fields work, how the editor works, DNS configuration, connecting an integration (Google Workspace, Microsoft 365, Zoho Mail, Front, …), conversion-tracking setup, plans and billing — and before telling a user something isn't possible. Results are excerpts: to read a full guide, pass the page path from a result to read_docs_page. Public documentation; needs no scope and touches no workspace data.
Inputs: query (required), context (required), language. Returns: results
send_feedbackSend feedback to the Scribe teamAInspect
Send a bug report, missing-capability request, or question straight to the Scribe team. When a tool fails unexpectedly, a capability the user needs is missing, or the docs can't answer their question, OFFER the user to report it — and only send after they agree (the report includes their workspace identity). Works with any valid API key, no extra scope. Returns { received: true } once accepted; the team reads every report.
Inputs: context (required), message (required), category (required), reporter, +1 more. Returns: data
send_test_emailSend yourself a test of a signatureAInspect
Mail the user a test of a signature's DRAFT, to their own inbox and no one else's: what publish would install (the published design when the signature has no draft), with one email's real values and no tracking. To see a design in a real mail client (dark mode, Outlook, a phone) before anyone gets it: use it instead of copying, assigning, publishing or installing a signature to check it. There is no recipient to set: it goes to the signed-in user's own address (sent_to in the result), never a teammate's or anyone else's. email_id chooses whose values show; the user's own by default. Sent in the background, usually within a minute. 10 an hour per user: 429 rate_limited past that, say so and stop. 422 on email_id when the user has no address in the workspace (ask whose values to show), or on draft_content when the signature has no design yet. Unknown signature or email → 404.
Inputs: context (required), signature_id (required), email_id. Returns: data
set_signature_recipient_rulesSet signature recipient rulesADestructiveIdempotentInspect
Set a signature's rule-based targeting: the smart-field conditions tree and/or the assign_to_all_future_emails flag (provide at least one). Replaces conditions wholesale; manual and org-unit targeting are untouched. An unknown field or bad operator fails with 422.
Inputs: context (required), signature_id (required), conditions, assign_to_all_future_emails. Returns: data
sync_teammatesSync teammates nowADestructiveInspect
Resync the workspace's team now, as the dashboard's Refresh does, instead of waiting for the daily sync: every activated teammates integration (a directory such as Google Workspace, Microsoft Entra ID or Zoho Mail) and smart fields integration (BambooHR, Okta, …) syncs, so new people, aliases and changed details (a job title) reach Scribe and their signatures. A teammates sync can add and remove teammates, a smart fields sync changes and clears their values; both install their signatures, and neither mails anyone. Takes no argument. The syncs run in the background: the result lists those started. An integration whose sync already runs, or that lost its access, is left out. 409 sync_already_running when every sync already runs, integration_access_lost when every integration must be reconnected first, no_integration_to_sync when none is connected (relay the dashboard link).
Inputs: context (required). Returns: data
update_assetUpdate an assetADestructiveIdempotentInspect
Update an asset's metadata (name and/or role) by UUID. The image bytes can't be changed — create a new asset to replace them. An unknown role returns 422.
Inputs: id (required), context (required), name, role. Returns: data
update_emailUpdate an email's addressADestructiveIdempotentInspect
Change an email's address (works for primary and alias addresses). Only available when the workspace manages its own team list — a directory integration returns a 409 conflict. The new address is validated → 422 on failure.
Inputs: id (required), address (required), context (required). Returns: data
update_folderRename a folderADestructiveIdempotentInspect
Rename an existing signature folder by UUID; the name is the only folder property you can change. The folder keeps its id and its signatures, so prefer this over create_folder plus delete_folder when only the name is wrong. To move a signature into or out of a folder, use update_signature with folder_id instead; to remove the folder, use delete_folder. Overwrites the previous name and returns the folder with its signature_count. Needs the folders:write scope; an unknown id returns 404 and a blank name 422.
Inputs: id (required), name (required), context (required). Returns: data
update_marketing_campaignUpdate a marketing campaignADestructiveIdempotentInspect
Update a marketing campaign by UUID. Only the fields you pass change (omit = leave as-is; content: null clears it). status is read-only — use schedule/pause/resume to change it. Invalid enums, unknown smart fields, or unknown signature templates return 422.
Inputs: id (required), context (required), name, content, +8 more. Returns: data
update_signatureUpdate a signatureADestructiveIdempotentInspect
Update a signature template by UUID. Stages draft_content (the working copy) — the live content only changes when you publish_signature. Only the fields you pass change (omit = leave as-is; draft_content: null / folder_id: null clear them). When editing draft_content, call get_content_schema first for the block-tree schema, enum values (incl. the non-obvious icon names), and a worked example; an invalid tree returns 422 naming each offending field and its allowed values. Blocks are CLOSED: every key you add must exist in the schema, so build each block by adapting the schema's example rather than attaching extra keys to carry styling or smart-field values — an invented key fails the whole update with unknown_property.
Inputs: id (required), context (required), name, priority, +3 more. Returns: data
update_signature_variantUpdate a signature variantADestructiveIdempotentInspect
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.
Inputs: kind (required), context (required), signature_id (required), hidden, +3 more. Returns: data
update_smart_fieldUpdate a smart fieldADestructiveIdempotentInspect
Change an existing custom smart field's definition: its label, kind, required flag or integration binding. Only the fields you pass change, and the field keeps its id, so templates and campaign conditions that reference it still point to it. Use create_smart_field for a new field, delete_smart_field to remove one, and update_teammate to set a teammate's value (this tool never writes values directly). Binding a new integration or attribute queues a re-sync of the teammates' values from it (integrations never fill url fields); unlinking stops the sync. Overwrites the previous definition and returns the field. Needs the smart_fields:write scope; default fields are read-only (422), the computed Email field is not addressable (404), and a taken label, an invalid kind or an unknown integration returns 422.
Inputs: id (required), context (required), kind, label, +3 more. Returns: data
update_teammateUpdate a teammate's smart fieldsADestructiveIdempotentInspect
Set a teammate's smart-field values. Pass the teammate's UUID and an array of { smart_field_id, value }. Only manually-editable fields change — integration-synced and image fields in the payload are ignored. Email addresses are managed separately, not here.
Inputs: id (required), context (required), smart_fields (required). Returns: data
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
The agentic email signature platform: one saved signature for your people and your AI agents.
Manage team email signatures: teammates, groups, templates, banner campaigns, click analytics.
Email signatures for French businesses: HTML generator, legal mentions per job, SPF/DKIM/DMARC
E-signatures for contracts and NDAs. Draft with AI, review, and send for signature.
Related MCP Servers
- AlicenseAqualityDmaintenanceSend documents for e-signature from Claude Desktop, Claude Code, Cursor, and other AI agents. Free DocuSign alternative.1562 npmMIT
- AlicenseNot gradedqualityDmaintenanceE-signature for AI agents. One unauthenticated call returns a sandbox API key (no account, no browser), then the agent can send documents for signature, check status, and download the sealed PDF plus Certificate of Completion.3 npmMIT
- AlicenseAqualityBmaintenanceLets AI agents send PDFs for e-signature (recognized under ESIGN and UETA), place fields, track signers, and pull an evidence package. Every signing event goes into a public hash chain, sealed daily, so anyone can verify a document without trusting the sender or the service. 100 documents a month free, no card.11MIT
- AlicenseAqualityCmaintenanceDocument signing for AI agents. Send markdown or PDF for two-party e-signing with a single tool call — handles PDF generation, email verification, and SHA-256 certified delivery.217 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.