Unified Apps Script MCP

auth_setup

Sets up OAuth credentials by auto-detecting a Desktop OAuth client. If none is found, opens the Google Auth Platform Clients page and detects downloaded JSON from Downloads.

Instructions

Auto-detect a Desktop OAuth client. If absent, open the Google Auth Platform Clients page; downloaded client JSON is auto-detected from Downloads.

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_setup"
  }
}

Input Schema

Name	Required	Description	Default
`clientFile`	No
`openBrowser`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 25, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already flag openWorldHint=true and idempotentHint=false, and the description adds concrete side effects: it may open the Google Auth Platform Clients page and reads the Downloads folder for client JSON. It does not explain what gets written or changed, but given the annotations, the added context is useful.

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?

Two sentences, front-loaded with the core action, and no filler. The conditional structure is compact and every clause adds meaning.

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?

For a 2-param, no-output-schema setup tool with external side effects, the description explains the happy-path flow but omits what happens after auto-detection, what the return value is, and how openBrowser=false changes behavior. It is adequate but has clear gaps.

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 0%, so the description must carry the parameter documentation. It connects clientFile to auto-detection from Downloads and implies openBrowser controls opening the page, but it does not specify clientFile format or the exact role of openBrowser. This is partial compensation only.

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 opens with a specific action ('Auto-detect a Desktop OAuth client') and explains the fallback behavior (open the Google Auth Platform Clients page). This distinguishes it from auth_login, auth_status, and auth_logout, though it doesn't explicitly name any sibling or state the final configured state.

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

Usage Guidelines3/5

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

The text gives an internal conditional (auto-detect; if absent, open page) but never tells an agent when to choose this tool over auth_login, auth_status, or auth_logout. There is no explicit 'use when...' or exclusion, so usage is only implied by the setup-focused phrasing.

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