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.

Input Schema

Name	Required	Description
`id`	Yes	The sequence ID
`bcc`	No	BCC email address for all outgoing emails
`name`	No	Sequence name
`lists`	No	Array of list UUIDs to associate with sequence
`steps`	No	Modify 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.
`folder`	No	General folder ID to move the sequence into. Must be a folder created without a type (i.e., not an email-sender folder).
`paused`	No	Pause or resume the sequence. Setting false resumes sending emails to recipients and requires confirm: true as the account holder's explicit approval.
`confirm`	No	Required when paused is false — confirms the account holder explicitly approved resuming the sequence
`delayTo`	No	Maximum delay in minutes
`senders`	No	Comma-separated sender UUIDs
`starred`	No	Star the sequence
`skip_esg`	No	Skip ESG detection
`timezone`	No	IANA timezone for sending emails, e.g. 'Asia/Calcutta' or 'America/New_York'
`delayFrom`	No	Minimum delay in minutes
`evergreen`	No	Enable evergreen sequence
`plainText`	No	Send as plain text email
`auto_reply`	No	Enable auto-reply detection
`riskyEmail`	No	Send to contacts with risky email status
`validEmail`	No	Send to contacts with valid email status
`scheduledAt`	No	Launch 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.
`delayEnabled`	No	Enable sending delay
`invalidEmail`	No	Send to contacts with invalid email status
`workspace_id`	No	Workspace ID this action applies to. When omitted, the current or default workspace is used.
`matchProvider`	No	Match email provider when sending
`checkEmailOpen`	No	Check if recipient opened previous email
`checkEmailClick`	No	Check if recipient clicked a link in previous email
`checkEmailReply`	No	Check if recipient replied to previous email
`launchTimingMode`	No	Launch timing mode
`emailSendingHours`	No	Custom email sending hours for each day of the week (Monday-Sunday). Must include all 7 days if provided.
`stopWhenReplyRecieved`	No	Stop sequence when recipient replies
`checkEmailBeforeSending`	No	Verify email before sending. When enabled user must approve email before they can be sent
`sendToOnlyVerifiedEmail`	No	Only send to verified emails
`stopWhenReplyRecievedWhen`	No	When 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

Name	Required	Description	Default
`result`	No	The raw result returned by the SalesBlink tool.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, so the bar is lower; the description still adds real behavior: recipient eligibility is limited to the account holder's own contactable audience and suppression/blocklist is always enforced regardless of parameters. It does not warn that a supplied steps array wholesale replaces the flowchart, though the schema does.

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 short sentences, front-loaded with purpose, then scope exclusion, then constraints. No filler, though given 33 parameters the text is on the thin side rather than excessive.

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?

With 33 params, an output schema, and rich field descriptions, the description sensibly focuses on guardrails and sibling routing rather than repeating fields. It could state partial-update semantics (which fields are optional vs. full replacement) to be fully complete for a destructive mutation.

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 33 parameters, so the schema carries parameter meaning. The description contributes only one cross-parameter rule (recipient eligibility plus always-on blocklist enforcement) and otherwise adds nothing beyond the schema.

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?

"Update Sequence Properties and State" names a specific verb and resource, and the very next sentence excludes archiving by naming archive_sequence. The word "State" stays slightly vague (pause/launch/status overlap with update_sequence_status), so it is clear but not fully differentiated.

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 routes archiving to archive_sequence and states a hard precondition for the launch/resume path (explicit user confirmation). It does not address when to use this vs update_sequence_status, which is a sibling that also touches sequence state.

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

All SalesBlink Cold Email tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.