Skip to main content
Glama

Disconnect a sending account

disconnect_sending_account
DestructiveIdempotent

Use this when the user wants a mailbox or a LinkedIn seat disconnected. Campaigns stop sending from it, and a mailbox's synced emails and warmup go with it. Its 30-day fee stops; days already paid for are not refunded. It cannot be undone here: the account would have to be connected again. 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": {
      "channel": "<channel>",
      "accountId": "<accountId>"
    },
    "name": "disconnect_sending_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYes`email` for a mailbox, `linkedin` for a LinkedIn seat.
accountIdYesThe account's id: a mailbox's address, or a LinkedIn seat's id as the list of sending accounts gives it.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds the substance an agent needs: campaigns stop sending, synced emails and warmup are removed for mailboxes, the 30-day fee stops with no refund for paid days, the action is irreversible here, and it is free. That is well beyond what the annotations declare.

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?

Four tight sentences, front-loaded with the usage trigger, then consequences, cost, and irreversibility in descending importance. No filler or repetition.

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?

For a destructive two-parameter tool with no output schema, the description covers the trigger, the side effects, the billing impact, and the reversibility limit. An agent has everything needed to warn the user before calling it.

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 coverage is 100% and both parameters are fully documented, including the channel enum and accountId formats. The description only restates the mailbox/seat duality, adding no syntax or edge-case detail beyond the schema, so baseline 3 applies.

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 (disconnect) and resource (mailbox or LinkedIn seat) with the channel distinction built in, so an agent can immediately separate it from get_sending_account and update_sending_account.

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?

"Use this when the user wants a mailbox or a LinkedIn seat disconnected" gives a clear triggering condition, and the irreversibility note implies reconnecting is the reverse path. It does not name an alternative tool or spell out when not to disconnect, so it stops short of full routing guidance.

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.

Resources