Skip to main content
Glama

List sending accounts

list_sending_accounts
Read-only

Use this when the user asks which mailboxes and LinkedIn seats are connected, or to find one's id. Returns each account with its channel, whether campaigns may send from it, and whether its sign-in still works; a mailbox also shows how many emails it sends a day, what is left of that today, and its warmup. Send channel to list only mailboxes or only LinkedIn seats. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_sending_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNoOnly mailboxes (`email`) or only LinkedIn seats (`linkedin`). Both when left out.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), yet the description still adds substantial value by enumerating what each returned record contains: channel, send eligibility, sign-in validity, daily send volume, remaining quota today, and warmup state. The "Free" note is a cost disclosure the annotations do not provide. It would need pagination or scaling information for a 5.

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 trigger condition is front-loaded in the first clause, and the return-value detail is packed into one semicolon-joined sentence with no filler. The density is high and the "Free." fragment is slightly clipped, but every clause carries information an agent needs.

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?

With no output schema, the description carries the burden of explaining returns and does so field by field (channel, send eligibility, auth status, volume, remaining, warmup). For a one-optional-parameter, read-only list tool that is sufficient to call it correctly and interpret the result.

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 the enum parameter is already documented with the same meaning ("Only mailboxes (`email`) or only LinkedIn seats (`linkedin`). Both when left out."). The description's "Send channel to list only mailboxes or only LinkedIn seats" restates the schema rather than adding default behavior or edge-case guidance, so the baseline of 3 applies.

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?

The description names the resource in user-facing terms ("mailboxes and LinkedIn seats") and the operation is a list, which is clear. It also hints at the get_sending_account distinction by saying the tool is useful "to find one's id," but it never states the contrast explicitly, so sibling differentiation is inferred rather than declared.

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 asks which mailboxes and LinkedIn seats are connected, or to find one's id" gives a concrete triggering condition rather than a vague summary. It stops short of naming the alternative (e.g. get_sending_account for a known single account) or stating when not to use it, so it sits below the top band.

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