Email Signatures

Use these tools to create and maintain reusable email signatures. Signatures help keep sender information, business details, and required legal content consistent across different messages.

For example, you can create a signature, update its content, connect it with a sender profile, or control how it is used for different types of email. The available signature and delivery options may expand over time.

MCP tools

Configure Email Signature Delivery

Tool name: configure-signature-delivery

Changes only assigned tag IDs and sender, reply, CC, BCC, recipient and sender-domain fields. Omitted fields stay unchanged. Every ID must already belong to the account; this tool never creates tags, addresses or domains. A changed sender address is checked against its verified domain, and the matching sender domain is derived and stored as the app would store it. Content, metadata and the digital business card stay unchanged.

Input schema

signatureIdinteger, >= 1required

ID of the signature whose delivery configuration is changed

tagIdsArray of integers or null, <= 50 items

Replacement tag IDs that already exist; ordinary signatures require at least one, and every tag must be unassigned to another signature, while the default signature may use an empty array

Default:null

senderProfileobject

Sender name and configured account address/domain values; reply options are also used for CC, BCC and recipient, empty strings clear optional fields, omitted fields stay unchanged, and the sender domain is derived when the sender address changes

Default:null

accountIdnull or integer, >= 1

User ID of the account that owns the signature; omit for the token account, or pass an accessible subaccount ID

Default:null

Input example

{
  "signatureId": 1,
  "tagIds": null,
  "senderProfile": null,
  "accountId": null
}