gmail-accounts
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_accountsA | (unconfigured) List configured accounts and local token state. Call this first. |
| searchC | (unconfigured) Search a mailbox with Gmail query syntax. |
| get_threadB | (unconfigured) Thread metadata and snippets; bodies via get_message. |
| get_messageC | (unconfigured) One message with bodies and attachment stubs. |
| get_attachmentC | (unconfigured) Download one attachment to a path. |
| list_labelsC | (unconfigured) List labels. |
| label_threadC | (unconfigured) Add or remove labels on a thread. |
| list_draftsC | (unconfigured) List drafts. |
| create_draftC | (unconfigured) Create a draft. Pass reply_to_message_id to keep it in-thread. |
| update_draftC | (unconfigured) Replace a draft's content. Invalidates any staged approval. |
| stage_sendA | (unconfigured) Freeze a draft and request human approval to send. Does NOT send. |
| sendA | (unconfigured) Send a draft that a human already approved via the gmail-approve CLI. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool targets a distinct operation: search, thread/message retrieval, attachment download, threading labels, and a clearly separated draft/stage/send pipeline. Even adjacent tools like get_thread and get_message are delineated by thread-level vs message-level detail.
Tool names mostly follow a predictable verb_noun snake_case pattern with list_*, get_*, and create_/update_ prefixes. The bare verbs search and send, plus stage_send, are minor deviations but still readable and consistent in style.
Twelve tools is well-scoped for a Gmail account server covering search, reading, attachments, labels, drafts, and sending. Each tool earns its place with no obvious redundancy.
Core email workflows are covered: search, read, download attachments, label threads, create/update drafts, and send through an approval flow. Minor gaps like creating labels, adding attachments to drafts, or managing read state are plausible but not critical to the server's apparent purpose.