Emailchaser

Update sender email warm-up

update_sender_email_warmup

Idempotent

Switches warm-up on or off and changes the warm-up ramp for up to 100 mailboxes in one call, applying the same settings to each. Only the settings provided change. Warm-up sends startLimit emails on the first day and adds increaseBy each sending day until it reaches capLimit a day; this is separate from campaign sending limits. A mailbox that has never warmed needs enabled: true to take any other setting, and is then enrolled with the defaults (2 a day, 2 more each day, up to 10 a day, weekdays only, UTC) plus the settings given. Raising capLimit on a mailbox that is already warming lifts today's target without restarting its ramp. Each mailbox succeeds or fails on its own: the result lists the updated mailboxes' settings, each with its healthScore (0-100, higher is better; null while warm-up is off or before 20 warm-up emails were checked), under updated, and any failures with the reason under failed.

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": {
      "ids": "<ids>"
    },
    "name": "update_sender_email_warmup"
  }
}

Input Schema

Name	Required	Description
`ids`	Yes	Sender email IDs to update (from list_sender_emails)
`enabled`	No	true switches warm-up on, false switches it off
`capLimit`	No	Most warm-up emails per day; the ramp stops here
`timezone`	No	IANA timezone for the warm-up send window, e.g. America/New_York
`increaseBy`	No	Warm-up emails added each sending day until the cap
`startLimit`	No	Warm-up emails on the first day
`weekdaysOnly`	No	Send warm-up emails Monday to Friday only
`enableReplies`	No	Let warm-up recipients reply, adding reply signals

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedSep 12, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations (idempotent, non-destructive) by disclosing partial-update semantics, batch fan-out with per-mailbox success/failure, the default enrollment profile (2/day, +2 daily, cap 10, weekdays, UTC), the ramp mechanics, and that raising capLimit lifts today's target without restarting. It also explains healthScore semantics including null cases.

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?

Dense but every sentence carries load: batch scope, partial update, ramp math, defaults, cap behavior, and response shape. The most load-bearing constraint (batch uniform settings) is front-loaded in the first sentence.

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

Completeness5/5

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

There is no output schema, and the description compensates by naming the result fields (updated with settings and healthScore, failed with reason). For an 8-parameter batch mutation it covers defaults, preconditions, and return shape with nothing essential missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns a 4 by explaining how startLimit, increaseBy and capLimit interact as a ramp, and by stating the enabled:true precondition for enrollment, meaning the schema alone does not convey.

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

Purpose5/5

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

States a specific verb set (switch on/off, change the ramp) against a named resource (warm-up) plus the batch scope of up to 100 mailboxes with uniform settings. It is clearly distinct from get_sender_email_warmup and from campaign-limit tools, which it explicitly calls out as separate.

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 strong conditional guidance: 'Only the settings provided change', and 'a mailbox that has never warmed needs enabled: true to take any other setting'. It does not explicitly name an alternative tool for reading warm-up state, but the enrollment prerequisite and the raise-capLimit-without-restart note give the agent enough to choose correctly.

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

All Emailchaser 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.

Resources

Need Help?