Skip to main content
Glama

SalesBlink Cold Email

Update Sequence

update_sequence
Destructive

Update Sequence Properties and State. Archiving is handled by archive_sequence. Recipients must be the account holder's own contactable audience and suppression/blocklist is always enforced. Changing launch settings to start sending emails 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": {
      "id": "<id>"
    },
    "name": "update_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe sequence ID
bccNoBCC email address for all outgoing emails
nameNoSequence name
listsNoArray of list UUIDs to associate with sequence
stepsNoModify sequence steps. 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}. When provided, the entire steps array replaces the existing flowchart.
folderNoGeneral folder ID to move the sequence into. Must be a folder created without a type (i.e., not an email-sender folder).
pausedNoPause or resume the sequence. Setting false resumes sending emails to recipients and requires confirm: true as the account holder's explicit approval.
confirmNoRequired when paused is false — confirms the account holder explicitly approved resuming the sequence
delayToNoMaximum delay in minutes
sendersNoComma-separated sender UUIDs
starredNoStar the sequence
skip_esgNoSkip ESG detection
timezoneNoIANA timezone for sending emails, e.g. 'Asia/Calcutta' or 'America/New_York'
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
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.
delayEnabledNoEnable sending delay
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
checkEmailOpenNoCheck if recipient opened previous email
checkEmailClickNoCheck if recipient clicked a link in previous email
checkEmailReplyNoCheck if recipient replied to previous email
launchTimingModeNoLaunch timing mode
emailSendingHoursNoCustom email sending hours for each day of the week (Monday-Sunday). Must include all 7 days if provided.
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. 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"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag this as destructive, open-world and non-read-only, but the description adds policy context the annotations cannot: suppression/blocklist enforcement on recipients, audience ownership constraints, and a hard confirmation gate for launches. It does not warn that supplying steps replaces the whole flowchart (that is only in the schema) nor describe failure behavior.

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

Conciseness5/5

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

Three short sentences, front-loaded with the purpose, then the sibling exclusion, then the two hard constraints. No filler, no repetition of the name, and the highest-risk constraint (launch confirmation) is placed last for emphasis.

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?

An output schema exists and the 35-parameter input schema is fully documented, so the description needn't carry return values or field syntax. It covers the non-obvious gotchas (archiving elsewhere, audience restriction, confirmation gate) but omits that a provided steps array wipes the existing flowchart - an important destructive consequence for a 35-param mutation tool.

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%, with rich per-parameter text (including the steps replacement semantics, send_as behavior, and ooo wait days), so the baseline is 3. The description restates the recipient/launch/confirm constraints at a high level but adds no syntax or format detail beyond what the schema already documents.

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?

States a specific verb+resource ("Update Sequence Properties and State") and explicitly routes archiving to archive_sequence, which differentiates it from a close sibling. It does not disambiguate against update_sequence_status, which also exists in the sibling list, so an agent must infer the boundary.

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?

Provides concrete when-to guidance: archiving goes to archive_sequence, recipients must be the account holder's own contactable audience, and launch/start-sending changes require explicit user confirmation. No exclusions are given relative to update_sequence_status, so the routing is clear but not complete.

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.