Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

ga4_auth_status

Verifies whether the local read-only GA4 OAuth connection is configured, helping you confirm access before querying Google Analytics data.

Instructions

Check whether the local read-only Google Analytics OAuth connection is configured.

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": "ga4_auth_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description still discloses two non-obvious traits: the check is against a local configuration rather than live remote validation, and the connection is read-only. It stops short of saying what happens when unconfigured or whether it makes any network call, but for a zero-parameter probe this is solid coverage.

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?

A single front-loaded sentence with no filler; every word ('local', 'read-only', 'OAuth', 'configured') constrains the meaning of the check.

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 tool is simple, but there is no output schema and no annotations, so the description is the only place a caller could learn what the check returns (boolean, status string, diagnostic detail). That gap is real, though minor given the low complexity.

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

Parameters4/5

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

The tool takes no parameters, so the baseline of 4 applies; there are no argument semantics the description needs to carry. Schema coverage is also 100% on an empty object, so nothing is left undocumented.

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 states a specific verb ('Check whether') applied to a precise resource ('the local read-only Google Analytics OAuth connection is configured'). Naming 'Google Analytics' distinguishes it from the sibling auth-status tools for Ads, GTM, and Search Console without the reader needing to open any schema.

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?

Usage is only implied: an agent can infer this is a precondition check before calling ga4_run_report or ga4_list_account_summaries, but the description never says so, nor does it say what to do when the check fails. No exclusions or alternatives are stated.

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