Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

ads_auth_status

Read-onlyIdempotent

Check Google Ads OAuth, developer-token, and customer-ID readiness before API calls, without revealing secret values.

Instructions

Check Google Ads OAuth, developer-token, and customer-ID readiness without revealing secrets.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds a meaningful guarantee not present in those annotations – that the check will not reveal secrets – which tells an agent it is safe to surface the result. It stops short of describing the readiness shape (per-credential pass/fail) the caller will receive.

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 lists the three credential components checked and closes with the secrecy constraint. No filler, no restatement of the tool name, nothing wasted.

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-parameter status probe with rich annotations, the definition covers what is inspected and the privacy guarantee. Since no output schema exists, it could say a bit more about what a successful versus failed readiness result looks like, but the gap is minor.

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 and the schema is an empty closed object, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly implies the check is scoped entirely by ambient configuration.

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) and a precisely scoped resource: Google Ads OAuth, developer-token, and customer-ID readiness. That naming separates it from the ga4_auth_status, gtm_auth_status, and search_console_auth_status siblings without needing to reference them explicitly.

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?

Preflight usage is implied by 'readiness' – an agent can infer it should confirm credentials before running report or keyword tools – but the description never says when to call it, when not to, or point to ads_list_accessible_customers as the alternative for enumerating customer IDs. The guidance is inferable rather than stated.

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