gsuite
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_CLIENT_ID | Yes | Your Google client ID | |
| GOOGLE_REDIRECT_URI | Yes | Your Google redirect URI | |
| GOOGLE_CLIENT_SECRET | Yes | Your Google client secret | |
| GOOGLE_OAUTH_CREDENTIALS | Yes | Your Google OAuth credentials |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| google-gmail_list_messagesC | List messages in user's mailbox with optional filtering |
| google-gmail_get_messageB | Get a specific message by ID |
| google-gmail_send_messageB | Send an email message. Requires message in RFC 2822 format encoded as base64url string |
| google-gmail_create_draftB | Create a new draft message. IMPORTANT: Message must be an object with 'raw' field containing base64url-encoded RFC 2822 formatted message. |
| google-gmail_delete_messageA | PERMANENTLY delete a message - IMMEDIATE and IRREVERSIBLE. WARNING: Use trash_message instead for normal email deletion. Only use this for sensitive data that must be immediately destroyed. Bypasses trash completely. REQUIRES https://mail.google.com/ scope. Returns 204 No Content with empty body on success. |
| google-gmail_modify_messageB | Modify labels on a message (add/remove labels, mark read/unread) |
| google-gmail_search_messagesD | search_messages endpoint for google-gmail |
| google-drive_list_filesC | List files in Google Drive with optional search query and filtering |
| google-drive_get_fileC | Get file metadata by ID |
| google-drive_update_fileC | Update file metadata |
| google-drive_delete_fileA | Permanently delete a file. Returns 204 No Content with empty body on success. |
| google-drive_search_filesB | Advanced file search with complex query syntax |
| google-drive_create_fileD | create_file endpoint for google-drive |
| google-drive_share_fileD | share_file endpoint for google-drive |
| google-calendar_list_eventsC | Returns events on the specified calendar |
| google-calendar_get_eventC | Returns an event |
| google-calendar_create_eventC | Creates an event |
| google-calendar_update_eventC | Updates an event |
| google-calendar_delete_eventA | Deletes an event. Returns 204 No Content with empty body on success. |
| google-calendar_list_calendarsB | Returns the calendars on the user's calendar list |
| google-contacts_create_contactB | Create a new contact with specified fields |
| google-contacts_update_contactA | Update an existing contact. IMPORTANT: Include the 'etag' field in the request body to prevent conflicts. Get the current etag by first calling get_contact or from a previous create/update response. |
| google-contacts_delete_contactB | Delete a contact permanently |
| google-contacts_search_contactsA | Search across all contacts with text query |
| google-contacts_list_contactsC | list_contacts endpoint for google-contacts |
| google-contacts_get_contactC | get_contact endpoint for google-contacts |
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 26 tools
Each tool targets a distinct action within its service (e.g., create, delete, get, list, update, search), and the service prefix clearly groups them. There is no ambiguity between tools like list and search because their descriptions specify different use cases.
All tool names follow a consistent pattern: service-toolname_verb_noun (e.g., google-calendar_create_event). Naming is fully uniform with underscores and no mixed conventions.
With 26 tools spanning four Google services, the count is on the higher side but still reasonable. Each service has a well-scoped set of operations (6–8 tools), and no tool feels redundant.
Calendar, Contacts, and Gmail cover CRUD operations plus search/list; Drive adds sharing. Minor gaps exist (e.g., no calendar update, no trash for Gmail), but these do not significantly impair common workflows.