Skip to main content
Glama

Update a sending account

update_sending_account
DestructiveIdempotent

Use this when the user wants to change a sending account's settings. A mailbox takes name, dailyCapacity (1 to 15 emails a day) and signature; a LinkedIn seat takes dailyLimits, weeklyLimits and signature, within what the seat allows. A field the account's channel does not take is refused. 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": "update_sending_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoMailboxes: the sender name recipients see. A seat's name is its LinkedIn profile's.
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.
signatureNoWhat `{Sender Signature}` inserts: HTML on a mailbox, up to 10,000 characters; plain text on a seat, up to 2,000. Empty removes it.
dailyLimitsNoSeats: `invitations` and `messages` a day, together. Free seats allow up to 20 and 80, premium seats up to 80 and 150.
weeklyLimitsNoSeats: `invitations` and `messages` a week, together. Free seats allow up to 100 and 400, premium seats up to 200 and 800.
dailyCapacityNoMailboxes: the most emails it sends a day, 1 to 15. Start a mailbox under 3 months old at 5.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the mutation/destructive and idempotent profile, so the description does not need to restate safety metadata. The description adds useful behavior beyond the schema by stating that channel-inappropriate fields are refused and that the operation is free, though it does not explain the destructiveHint implications or what existing settings may be overwritten.

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 short and front-loads the main usage condition, then adds channel-specific field rules. The trailing one-word sentence 'Free.' is terse and slightly ambiguous, but the overall structure is efficient.

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 seven parameters, nested objects, no output schema, and strong annotation coverage, the description gives enough context to select the tool and understand channel-specific constraints. It does not need to explain return values because no output schema is provided, though additional clarity on destructive effects could improve completeness.

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% and the schema already documents the channel-specific meanings, ranges, and nested limit objects. The description consolidates which fields apply to mailboxes versus LinkedIn seats and adds the refusal rule, but most parameter meaning is still supplied by the schema itself.

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 opens with a specific verb and resource: changing a sending account's settings. It also distinguishes the two account types handled by the tool, so an agent can tell this is the settings-update operation for sending accounts rather than list, get, or disconnect.

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 gives a clear when-to-use condition: when the user wants to change a sending account's settings. It does not name when not to use it or point to any sibling alternative, so it falls short of the strongest guidance level.

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