Skip to main content
Glama
dipseth

google-workspace-unlimited

Google Services OAuth Setup with Browser Support

start_google_auth
Idempotent

Initiate Google OAuth2 authentication to access Google services like Drive, Gmail, and Calendar with automatic browser opening and service selection.

Instructions

Initiate Google OAuth2 authentication flow for Google services with automatic browser opening (Drive, Gmail, Docs, Sheets, Slides, Calendar, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
auth_methodNoAuthentication method: - 'pkce_file': PKCE with file storage (recommended, default) - 'pkce_memory': PKCE with session-only storage - 'file_credentials': Legacy credential file methodpkce_file
service_nameNoService specification for authentication. Can be: - List of service names: ['drive', 'gmail', 'calendar'] for pre-selected services - String display name: 'My Custom App' for custom labeling (no pre-selection) - None/empty: Uses common service defaults
auto_open_browserNoAutomatically open browser for authentication
user_google_emailNoGoogle email address for authentication
cross_oauth_passwordNoPassphrase for cross-OAuth account access. Provide this when accessing a linked account that requires a passphrase. Only alphanumeric, underscore, and hyphen allowed.
show_service_selectionNoShow service selection UI before authentication

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoAdditional notes or warnings about the authentication
errorNoError message if authentication failed
statusYesAuthentication status
authUrlNoOAuth2 authorization URL to open in browser for user consent
messageYesHuman-readable message describing the authentication status
sessionIdNoSession UUID for this connection. Save this to reconnect with same tool state using ?uuid= parameter
userEmailYesGoogle email address being authenticated
serviceNameNoList of Google services being authorized (e.g., ['drive', 'gmail', 'calendar'])
instructionsNoStep-by-step instructions for completing the OAuth flow
clickableLinkNoFormatted clickable link for terminal/UI display
scopesIncludedNoList of OAuth scopes being requested for the selected services
Behavior4/5

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

Description adds context about automatic browser opening, which complements annotations. Annotations already declare non-destructive and idempotent behavior; description clarifies the interactive nature.

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

Conciseness4/5

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

Single sentence is efficient and front-loaded with the main action, though listing services inline slightly reduces readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Lacks essential context such as when this tool should be called (e.g., before other Google tools), prerequisites, or what happens after successful authentication. With an output schema, some details may be there, but description remains insufficient.

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

Parameters3/5

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

Schema coverage is 100% with detailed parameter descriptions. The tool description adds no additional parameter information beyond what the schema provides.

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?

The description clearly states it initiates Google OAuth2 authentication flow for various Google services, distinguishing it from sibling tools that perform specific CRUD operations on those services.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, or prerequisites like needing credentials files beforehand. Does not mention that it may be unnecessary if already authenticated.

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/dipseth/google_workspace_fastmcp2'

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