Skip to main content
Glama
Sign In
Gmail Multi-Inbox MCP Server

Gmail Multi-Inbox MCP Server

by tszaks
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

finish_account_auth

Finish account authentication by exchanging the authorization code and storing token.json, enabling secure Gmail access.

Instructions

Complete OAuth onboarding by exchanging authorization code and storing token.json.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account_id": "<account_id>",
      "authorization_code": "<authorization_code>"
    },
    "name": "finish_account_auth"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idYesAccount id used in begin_account_auth.
authorization_codeYesOAuth authorization code from Google redirect.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.2

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly mentions the side effect of 'storing token.json' and the exchange of an authorization code, but does not disclose potential failure modes, whether it overwrites an existing token, or prerequisites beyond what is implied by the schema.

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

Conciseness5/5

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

The description is a single concise sentence that front-loads the purpose and includes the key side effect. Every word earns its place, with no redundancy or filler.

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

Completeness4/5

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

For a simple two-parameter tool with no output schema and no annotations, the description adequately covers the core purpose and primary side effect. It could be slightly more complete by explicitly mentioning the prerequisite relationship to 'begin_account_auth', but the context is strongly implied and sufficient for an agent.

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 description coverage is 100% for both parameters, so the description need not add additional parameter detail. The description does not introduce semantics beyond what the schema already provides, earning the baseline score of 3.

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 the tool's function with a specific verb ('Complete'), the resource ('OAuth onboarding'), and the mechanism ('exchanging authorization code and storing token.json'). It also differentiates from the sibling tool 'begin_account_auth' by indicating completion of the flow.

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

Usage Guidelines4/5

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

The description implies usage context through the word 'Complete' and the reference to 'authorization code', suggesting it follows 'begin_account_auth'. However, it does not explicitly state 'use after begin_account_auth' or mention exclusions, though the sibling tool name and schema description for account_id provide strong contextual cues.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools