Skip to main content
Glama

infomaniak_get_mailbox_full

Read-onlyIdempotent

Retrieve complete mailbox details including auto-responder, aliases, redirections, login history, password age, size, trusted devices, DKIM, SMTP ban, filtering rules, and associated users/teams for audits or onboarding.

Instructions

Full mailbox detail: auto-responder (vacation reply) state + content, aliases, redirections, IMAP/POP3 last login, password age, size on disk, trusted devices count, DKIM signature flag, SMTP ban status, Gmail-style filtering (commercials/social_networks), authorized/blocked senders, attached users + teams. Useful for mailbox audits and onboarding flows. Manager-private.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mail_hosting_idYes
mailbox_nameYesLocal part of the mailbox (e.g. 'anthony' for anthony@coden.lu).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
mailbox_nameYes
mailboxYes
mailbox_idnNo
noteNo
typeNo
is_limitedNo
is_free_mailNo
is_used_for_accountNo
count_signaturesNo
count_invitationsNo
count_devicesNo
has_auto_responderNo
auto_responderNo
has_redirectionNo
redirectionNo
aliasesNo
full_aliasesNo
created_atNo
password_last_changed_atNo
sizeNoMailbox size on disk in bytes.
size_checked_atNo
imap_last_login_atNo
pop3_last_login_atNo
usersNo
teamsNo
has_move_spamNo
authorized_sendersNo
blocked_sendersNo
has_dkim_signatureNo
smtpban_bounceNo
smtpban_authNo
smtpban_urlNo
has_mail_filteringNo
mail_filtering_folder_commercialsNo
mail_filtering_folder_social_networksNo
has_legacy_deviceNo
has_multi_passwordNo
external_mail_flag_enabledNo
count_usersNo
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint. Description adds value by listing specific fields returned and noting 'Manager-private' access restriction, which goes beyond what annotations provide. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is a single verbose sentence listing many fields; it is adequately concise but could be more structured (e.g., bullet list) for easier scanning. Purpose is front-loaded.

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?

Given the existence of an output schema, the description sufficiently covers the tool's return content and access context. It explains what fields are included and mentions use cases, but does not address relationship with similar tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% (only mailbox_name has a description). The description does not add any parameter documentation beyond the schema, leaving the mail_hosting_id parameter undocumented.

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?

Description clearly states it returns 'Full mailbox detail' and lists many specific fields, distinguishing it from the sibling 'infomaniak_get_mailbox_info' by name and scope. However, it does not explicitly contrast with that sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description provides usage context ('useful for mailbox audits and onboarding flows'), but does not explicitly state when not to use it or mention alternatives like get_mailbox_info for basic queries.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Mogacode-ma/infomaniak-mcp-agent'

If you have feedback or need assistance with the MCP directory API, please join our Discord server