Skip to main content
Glama

SalesBlink Cold Email

Update Sender

update_sender
Destructive

Update Sender - Update email sender settings (warmup, inbox, signature, tracking domain, etc.)

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_sender"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe sender ID
folderNoEmail-sender folder ID to move the sender into. Must be a folder created with type 'email-sender'. An empty string removes the sender from its current folder.
reply_toNoReply-to email address
open_rateNoOpen rate percentage (1-100)
signatureNoSignature ID or name
spam_pathNoSpam folder path
inbox_pathNoInbox folder path
warmup_urlsNoWarmup link IDs (the id values from get_warmup_links) to insert into warmup emails. An empty array removes all links. Requires a plan with warmup links.
workspace_idNoWorkspace ID this action applies to. When omitted, the current or default workspace is used.
inbox_enabledNoEnable inbox monitoring
read_emulationNoRead emulation percentage (1-100)
warmup_enabledNoEnable/disable warmup
warmup_keywordNoWarmup filter tag: two words joined by a dash, e.g. 'blue-river'. It is included in every warmup email so the user can filter them.
dkim_identifierNoDKIM identifier
spam_protectionNoSpam protection percentage (1-100)
tracking_domainNoTracking domain ID
warmup_scheduleNoDays and time slots when warmup emails and replies may be sent. null switches the schedule off and keeps its days.
warmup_templatesNoIDs of this workspace's email templates to warm up. An empty array removes all. Requires a plan with warmup templates.
ramp_up_frequencyNoDaily increment when auto ramp-up is on (1-50)
max_daily_frequencyNoDaily warmup limit (1-50). With auto ramp-up off this is the daily limit; with it on, the ceiling.
auto_ramp_up_enabledNoEnable auto ramp-up: start at starting_warmup_frequency and add ramp_up_frequency each day up to max_daily_frequency
starting_warmup_frequencyNoInitial daily limit when auto ramp-up is on (1-50)
sequence_ramp_up_frequencyNoSequence ramp-up increment
use_custom_tracking_domainNoUse custom tracking domain
sequence_max_daily_frequencyNoMax daily sequence sends
sequence_auto_ramp_up_enabledNoEnable sequence auto ramp-up
sequence_initial_daily_frequencyNoInitial daily sequence sends
pause_cold_emails_when_health_lowNoPause cold emails when health is low
pause_cold_emails_health_thresholdNoHealth threshold to pause at

Output Schema

NameRequiredDescriptionDefault
resultNoThe raw result returned by the SalesBlink tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed29 schema fields changed
    • changedInput schema / properties / auto_ramp_up_enabled / description
      Previous value: -"Enable auto ramp-up"New value: +"Enable auto ramp-up: start at starting_warmup_frequency and add ramp_up_frequency each day up to max_daily_frequency"
    • changedInput schema / properties / max_daily_frequency / description
      Previous value: -"Max daily warmup emails"New value: +"Daily warmup limit (1-50). With auto ramp-up off this is the daily limit; with it on, the ceiling."
    • addedInput schema / properties / max_daily_frequency / maximum
      Added value: +50
    • addedInput schema / properties / max_daily_frequency / minimum
      Added value: +1
    • changedInput schema / properties / max_daily_frequency / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / open_rate / description
      Previous value: -"Target open rate percentage"New value: +"Open rate percentage (1-100)"
    • addedInput schema / properties / open_rate / maximum
      Added value: +100
    • addedInput schema / properties / open_rate / minimum
      Added value: +1
    • changedInput schema / properties / open_rate / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / ramp_up_frequency / description
      Previous value: -"Ramp-up increment"New value: +"Daily increment when auto ramp-up is on (1-50)"
    • addedInput schema / properties / ramp_up_frequency / maximum
      Added value: +50
    • addedInput schema / properties / ramp_up_frequency / minimum
      Added value: +1
    • changedInput schema / properties / ramp_up_frequency / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / read_emulation / description
      Previous value: -"Read emulation level"New value: +"Read emulation percentage (1-100)"
    • addedInput schema / properties / read_emulation / maximum
      Added value: +100
    • addedInput schema / properties / read_emulation / minimum
      Added value: +1
    • changedInput schema / properties / read_emulation / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / spam_protection / description
      Previous value: -"Spam protection level"New value: +"Spam protection percentage (1-100)"
    • addedInput schema / properties / spam_protection / maximum
      Added value: +100
    • addedInput schema / properties / spam_protection / minimum
      Added value: +1
    • changedInput schema / properties / spam_protection / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / starting_warmup_frequency / description
      Previous value: -"Starting warmup frequency"New value: +"Initial daily limit when auto ramp-up is on (1-50)"
    • addedInput schema / properties / starting_warmup_frequency / maximum
      Added value: +50
    • addedInput schema / properties / starting_warmup_frequency / minimum
      Added value: +1
    • changedInput schema / properties / starting_warmup_frequency / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / warmup_keyword / description
      Previous value: -"Warmup keyword/tag"New value: +"Warmup filter tag: two words joined by a dash, e.g. 'blue-river'. It is included in every warmup email so the user can filter them."
    • addedInput schema / properties / warmup_schedule
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "days": {
      +          "description": "Omitted: keeps the stored days",
      +          "items": {
      +            "additionalProperties": false,
      +            "properties": {
      +              "enabled": {
      +                "type": "boolean"
      +              },
      +              "name": {
      +                "enum": [
      +                  "Sunday",
      +                  "Monday",
      +                  "Tuesday",
      +                  "Wednesday",
      +                  "Thursday",
      +                  "Friday",
      +                  "Saturday"
      +                ],
      +                "type": "string"
      +              },
      +              "slots": {
      +                "description": "Up to 4 non-overlapping slots",
      +                "items": {
      +                  "additionalProperties": false,
      +                  "properties": {
      +                    "fromTime": {
      +                      "description": "Whole hour 'HH:00', 00:00-23:00",
      +                      "type": "string"
      +                    },
      +                    "toTime": {
      +                      "description": "Whole hour 'HH:00', 01:00-24:00, after fromTime",
      +                      "type": "string"
      +                    }
      +                  },
      +                  "required": [
      +                    "fromTime",
      +                    "toTime"
      +                  ],
      +                  "type": "object"
      +                },
      +                "maxItems": 4,
      +                "type": "array"
      +              }
      +            },
      +            "required": [
      +              "name",
      +              "enabled"
      +            ],
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "enabled": {
      +          "description": "true: send warmup emails only in the slots below. false: send throughout the day.",
      +          "type": "boolean"
      +        },
      +        "timezone": {
      +          "description": "IANA timezone the slot times are in, e.g. 'America/New_York'. Omitted: keeps the stored timezone (UTC if none).",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "enabled"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Days and time slots when warmup emails and replies may be sent. null switches the schedule off and keeps its days."
      +}
    • changedInput schema / properties / warmup_templates / description
      Previous value: -"Warmup template IDs"New value: +"IDs of this workspace's email templates to warm up. An empty array removes all. Requires a plan with warmup templates."
    • changedInput schema / properties / warmup_urls / description
      Previous value: -"Warmup link URLs"New value: +"Warmup link IDs (the id values from get_warmup_links) to insert into warmup emails. An empty array removes all links. Requires a plan with warmup links."
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is partially covered, but the description adds nothing beyond restating fields. It never discloses the crucial behavioral fact that this is a partial update (omitted fields are preserved), nor what data is overwritten when a field like warmup_schedule or warmup_urls is supplied.

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?

A single compact sentence with the key information front-loaded and no filler. The redundant 'Update Sender -' title prefix is the only minor waste.

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

Completeness2/5

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

For a 29-parameter, destructive, partial-update mutation with nested schedule objects, a one-line description is far too thin. It omits update semantics (merge vs replace), interactions between fields (e.g. auto_ramp_up_enabled with starting/ramp_up/max frequencies), plan-gated fields, and confirmation/caution guidance for a destructive operation.

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%, including detailed nested docs for warmup_schedule, so the schema carries the parameter semantics. The description's list of setting categories (warmup, inbox, signature, tracking domain) is mildly useful orientation but adds no syntax or conditional detail 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?

Uses a specific verb ('Update') with a specific resource ('email sender settings') and enumerates several affected setting areas (warmup, inbox, signature, tracking domain). It does not name or differentiate itself from siblings like get_all_senders or update_user, but a reader can immediately tell what it modifies.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this versus alternatives (e.g. add_user, reconnect_sender, get_all_senders) and no prerequisites such as required permissions or plan restrictions. The 'update' verb implies usage, but the agent is left to infer everything about selection.

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.