FastMCP Gmail Reader Server
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_emailsA | Fetch recent emails from Gmail inbox. Args: max_results: Number of emails to fetch. page_token: Optional page token to fetch next batch. Returns: Dictionary containing: - email_list: List of email summaries. - nextPageToken: Token to retrieve more emails if available. |
| create_reply_draftC | Create a reply draft for an email with the given reply text. Args: email_id: The ID of the email to reply to. reply_text: The text content of the reply. Returns: A status message about the draft creation. |
| create_new_email_draftA | Create a new draft email (not a reply). Args: recipient: Email address to send to (can be empty to leave blank). subject: Subject of the email. body_text: Body content of the email. Returns: A status message about the draft creation. |
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 3 tools
Each tool has a clearly distinct purpose: create_new_email_draft for new emails, create_reply_draft for replies, and read_emails for fetching emails. There is no overlap in functionality, making it easy for an agent to select the right tool.
All tools follow a consistent verb_noun pattern with snake_case: create_new_email_draft, create_reply_draft, and read_emails. The naming is predictable and readable throughout the set.
With only 3 tools, the server feels thin for a Gmail reader, as it lacks operations like updating drafts, deleting emails, or managing labels. While the core functions are present, the scope is limited compared to typical email management needs.
The tool set is severely incomplete for a Gmail server. It only supports creating drafts and reading emails, missing essential CRUD operations like sending emails, updating drafts, deleting emails, or accessing other Gmail features such as labels or attachments. This will likely cause agent failures in broader email workflows.