Skip to main content
Glama

SalesBlink Cold Email

Create Sequence

create_sequence

Create a Sequence - Create a new email sequence/campaign. Recipients must be the account holder's own contactable audience (e.g. their own opt-in or otherwise consented contacts) — never addresses assembled by the model — and suppression/blocklist is always enforced. Sequences are created paused by default; launching (resuming) sends emails to recipients and must only happen after explicit user confirmation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "senders": "<senders>",
      "lists": "<lists>",
      "steps": "<steps>"
    },
    "name": "create_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
bccNoBCC email address for all outgoing emails
nameYesName of the sequence
listsYesArray of list UUIDs to include in the sequence
stepsYesSequence steps. Required and non-empty. Each email step must be {type: 'email', template_id: 'public-template-uuid'} with optional send_as: 'new' | 'followup' (followup replies in the existing thread; ignored on the first email step, which always starts a new thread). Each delay step must be {type: 'delay', days: number}.
folderNoOptional general folder ID to organize the sequence. Must be a folder created without a type (i.e., not an email-sender folder).
pausedNoWhether to create the sequence in paused state. Default true (the API pauses new sequences when omitted). When false, the sequence launches and starts sending emails (in ~5 mins with launchTimingMode 'now', or at scheduledAt when 'schedule') and requires confirm: true as the account holder's explicit approval.
confirmNoRequired when paused is false — confirms the account holder explicitly approved launching the sequence
delayToNoMaximum delay in minutes
sendersYesComma-separated sender UUIDs
starredNoWhether to star the sequence
skip_esgNoSkip ESG detection
timezoneNoIANA timezone for scheduled sending, e.g. 'Asia/Calcutta' or 'America/New_York'. Required when launchTimingMode='schedule'; otherwise it defaults to UTC.
autoPauseNoEnable auto-pause
delayFromNoMinimum delay in minutes
evergreenNoEnable evergreen sequence
plainTextNoSend as plain text email
auto_replyNoEnable auto-reply detection
riskyEmailNoSend to contacts with risky email status
validEmailNoSend to contacts with valid email status
bouncePauseNoPause on bounce threshold reached
scheduledAtNoLaunch time. UTC milliseconds OR an ISO 8601 datetime with timezone offset, e.g. '2026-07-08T16:30:00+05:30' for 4:30 PM IST. Required when launchTimingMode='schedule'.
delayEnabledNoEnable sending delay between emails
invalidEmailNoSend to contacts with invalid email status
workspace_idNoWorkspace ID this action applies to. When omitted, the current or default workspace is used.
matchProviderNoMatch email provider when sending
autoTagRepliesNoTag each reply's outcome with AI. Defaults to true when your plan includes AI reply tagging. Works only when checkEmailReply is on.
checkEmailOpenNoCheck if recipient opened previous email
bounceThresholdNoBounce threshold before pausing
checkEmailClickNoCheck if recipient clicked a link in previous email
checkEmailReplyNoCheck if recipient replied to previous email
launchTimingModeNoWhen to launch: 'now' (default, starts in ~5 mins) or 'schedule'
emailSendingHoursNoCustom email sending hours for each day of the week (Monday-Sunday). Default: weekdays 09:00-17:00 enabled, weekends disabled.
stopOnOutOfOfficeNoStop the sequence for a lead when they send an out-of-office or other automatic reply. When false (default), the lead's next emails wait until the day after the return date in the reply.
outOfOfficeWaitDaysNoIf an out-of-office or automatic reply has no return date, the number of days after the reply to wait before the lead's next email. Whole number from 1 to 90, default 7. Ignored when stopOnOutOfOffice is true.
stopWhenReplyRecievedNoStop sequence when recipient replies
checkEmailBeforeSendingNoVerify email before sending. When enabled user must approve email before they can be sent
sendToOnlyVerifiedEmailNoOnly send to verified emails
stopWhenReplyRecievedWhenNoWhen to stop sequence on reply: 'contact' = stop for this contact only, 'contact-with-same-domain' = stop for all contacts sharing the same domain

Output Schema

NameRequiredDescriptionDefault
resultNoThe raw result returned by the SalesBlink tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / timezone / description
      Previous value: -"IANA timezone for scheduled sending, e.g. 'Asia/Calcutta' or 'America/New_York'. Required when launchTimingMode='schedule'; otherwise it defaults to America/New_York."New value: +"IANA timezone for scheduled sending, e.g. 'Asia/Calcutta' or 'America/New_York'. Required when launchTimingMode='schedule'; otherwise it defaults to UTC."
  2. Changed1 schema field changed
    • changedInput schema / properties / autoTagReplies / description
      Previous value: -"Auto-tag replies"New value: +"Tag each reply's outcome with AI. Defaults to true when your plan includes AI reply tagging. Works only when checkEmailReply is on."
  3. Changed2 schema fields changed
    • addedInput schema / properties / outOfOfficeWaitDays
      Added value: +{
      +  "description": "If an out-of-office or automatic reply has no return date, the number of days after the reply to wait before the lead's next email. Whole number from 1 to 90, default 7. Ignored when stopOnOutOfOffice is true.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / stopOnOutOfOffice
      Added value: +{
      +  "description": "Stop the sequence for a lead when they send an out-of-office or other automatic reply. When false (default), the lead's next emails wait until the day after the return date in the reply.",
      +  "type": "boolean"
      +}
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare only that this is a non-read-only, non-destructive, open-world write. The description adds substantive behavior the annotations cannot convey: sequences are created paused by default, suppression/blocklist is always enforced, and resuming actually sends email. It does not clarify rate limits, permission requirements, or what the returned object contains, but the core safety profile is well covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three front-loaded sentences with no filler, and the safety constraints arrive before any optional detail. The opening 'Create a Sequence - Create a new email sequence/campaign' redundantly restates the title, which is the only waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 38-parameter creation tool with an output schema and full schema coverage, the description only needs to carry the non-schema risk surface, which it does: consent of recipients, blocklist enforcement, and default-paused creation. Nothing an agent needs in order to invoke it safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% across all 38 parameters, so the schema already documents names, defaults, enums, and conditional requirements. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Create a new email sequence/campaign'), so the agent knows exactly what is produced. It never names a sibling such as update_sequence or clone_sequence to delineate create-from-modify, so it stops short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It sets clear usage context: this is the creation path, recipients must come from the account holder's own consented audience, and launching must follow explicit user confirmation. It gives strong when- and when-not-to-launch guidance but does not point to any alternative tool for modifying or duplicating an existing sequence.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.