Conecto

Change an outreach mailbox

outreach_update_mailbox

Change a connected mailbox: the name people see (sender_name), its daily limit (1 to 200 emails in any 24 hours, shared by every campaign that sends from it), pause or resume its sending, or disconnect it (Conecto forgets its password). A campaign none of whose mailboxes can send pauses and tells you; resume it once a mailbox can send again. Its settings and password change only on a new connect link (outreach_connect_mailbox). Free.

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": {
      "mailbox_id": "<mailbox_id>"
    },
    "name": "outreach_update_mailbox"
  }
}

Input Schema

Name	Required	Description
`paused`	No
`disconnect`	No	true disconnects it for good.
`mailbox_id`	Yes
`daily_limit`	No
`sender_name`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.7/5.0

Behavior1/5

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

The description contradicts the destructiveHint: false annotation by stating that disconnect is permanent and that Conecto forgets the password. This is a material behavioral contradiction, since the tool can perform a destructive disconnect despite annotations declaring otherwise.

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?

The description is front-loaded with the core change operation and remains dense without much repetition. It is slightly dense with campaign consequence and pricing details, but every sentence largely supports correct invocation.

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 mutation tool with no output schema and low schema description coverage, the description supplies the important side effects, limitations, and alternative tool. The only significant gap is the annotation contradiction around destructiveness, which undermines confidence in safety behavior.

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?

Although schema description coverage is only 20%, the description compensates well: it explains sender_name, daily_limit (including range and shared campaign impact), paused, and disconnect semantics beyond the schema. The required mailbox_id is not described but is self-evident from the tool purpose.

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?

The description states a precise verb and resource: changing a connected outreach mailbox. It enumerates the specific updateable fields (sender_name, daily_limit, paused, disconnect) and distinguishes settings/password changes by pointing to outreach_connect_mailbox.

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 clearly establishes when to use this tool for mailbox changes and explicitly routes settings/password changes to outreach_connect_mailbox. It also explains the operational consequence for campaigns when no mailbox can send, though it does not explicitly distinguish from sibling campaign pause/resume tools.

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

All Conecto 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?