Skip to main content
Glama

maily_list_accounts

Lists all email profiles available in Maily, including ID, email, name, and color, so you can use the email or name as the profile parameter for other tools.

Instructions

Lists the email profiles available in Maily (id, email, name, color). Use the email or the name as the profile parameter of the other tools.

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": "maily_list_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so the description carries the burden. It indicates a read-only listing implicitly by 'lists' and reveals the return fields, but doesn't state side effects, auth requirements, or whether results are cached/complete. Adequate but not rich.

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?

Two short sentences, front-loaded with the action and return fields, then the usage hint. No wasted words.

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?

An output schema exists, so return values need not be explained further, and the description already summarizes them. For a zero-param list tool that's nearly complete; only auth/behavioral notes are 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?

Zero parameters, so baseline is 4. The description still adds meaning by pointing out that the returned 'id/email/name' values are what feed the `profile` parameter elsewhere, which is genuinely useful cross-tool semantics.

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?

Specific verb (lists) + resource (email profiles/accounts in Maily), and it enumerates the returned fields (id, email, name, color), so an agent understands exactly what it gets. Clearly distinguished from siblings like maily_list_messages or maily_search.

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?

The second sentence gives concrete downstream usage: use email or name as the `profile` parameter of other tools, which tells the agent when to call this first. It stops short of naming when-not-to-use or alternatives, but the invocation context is clear.

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