Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

gtm_auth_status

Read-onlyIdempotent

Checks whether the local Google Tag Manager OAuth connection is configured and reports which scopes were granted.

Instructions

Check whether the local Google Tag Manager OAuth connection is configured and which scopes were granted.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile needs no restating. The description adds useful context — that it inspects a connection rather than doing data work, and that it discloses granted scopes — but says nothing about failure behavior when the connection is absent, or about how the scope list is formatted.

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 sentence, front-loaded on the check itself, followed by the two results it returns. No filler, no restatement of the title.

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 zero-param tool with no output schema, the description carries the burden of explaining return content and does so at a high level (configured or not, granted scopes). What is missing is only the edge-case behavior, such as what is returned or raised when no connection exists.

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 there is nothing for the description to disambiguate beyond schema coverage. The baseline of 4 applies for a zero-argument tool.

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 pairs the verb 'Check' with a specific resource — the local Google Tag Manager OAuth connection — and states both facts it reports (configured status and granted scopes). Naming Google Tag Manager makes it distinguishable from the ads/ga4/search_console auth_status siblings, though it never explicitly routes among them.

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?

Use is only implied: an agent can infer this is a prerequisite/verification call before invoking gtm_* operations, but the description never says when to call it (e.g. before a first operation, or on an auth failure) or what to do with a negative result. No explicit alternatives or exclusions are given.

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