Unified Apps Script MCP

auth_login

Run the Google OAuth PKCE flow in the system browser and store owner-only refresh credentials to enable authorized access to Apps Script and Workspace APIs.

Instructions

Open the system browser, run Google OAuth with PKCE and a one-shot loopback callback, then store owner-only refresh credentials.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "auth_login"
  }
}

Input Schema

Name	Required	Description	Default
`profile`	No		apps-script
`timeoutSeconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 25, 2026

TDQS

B3.3/5.0

Behavior4/5

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

The description goes beyond the sparse annotations by disclosing that the tool opens a browser, uses PKCE with a one-shot loopback callback, and persists owner-only refresh credentials. This gives a clear picture of the side effects, although it does not mention failure modes or behavior when credentials already exist.

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 dense sentence with no waste. The most important behavioral details, browser opening and OAuth flow, are front-loaded before the credential store outcome.

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

Completeness3/5

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

The core flow and credential-storing side effect are covered, but with no output schema the return behavior is undefined. The description also omits success/failure expectations, timeout behavior, and the relationship to auth_setup, leaving some uncertainty for an agent.

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

Parameters2/5

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

Schema description coverage is 0%, and the tool description does not explain either profile or timeoutSeconds. The enum values hint at OAuth scope profiles, but an agent is left to infer what 'profile' controls and how timeoutSeconds influences the login flow.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action: open the system browser, run Google OAuth with PKCE, and store owner-only refresh credentials. This clearly communicates what the tool does and distinguishes it from auth_status and auth_logout, though it does not explicitly differentiate it from the similarly named auth_setup sibling.

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?

The description does not state when to use auth_login versus auth_setup, auth_status, or google_workspace_request. It implies use during interactive login but provides no exclusions, prerequisites, or alternative routing.

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