Gmail MCP Server

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

6/6 tools missing one or more hints — search_emails (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_email (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); download_attachment (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — reauth deletes at line 249 (token_path.unlink())

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tool inputs are validated

4/6 tool handlers declare input schemas (67%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 2/6 tool handlers wrap calls in try/catch (33%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

No access to sensitive paths

Reads sensitive paths: GMAIL_CREDENTIALS_PATH, GMAIL_CREDENTIALS_PATH

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

Tool description accuracy

auth_status: accesses sensitive paths not mentioned in description

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.