Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

search_console_auth_status

Check whether the local read-only Search Console OAuth connection is configured before querying Search Console data.

Instructions

Check whether the local read-only Search Console 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": "search_console_auth_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful traits: the connection is "local" (credentials held locally) and "read-only" (no mutating scope is granted). It does not say whether the check performs a network round-trip, how it behaves when credentials are absent or expired, or what form the status comes back in.

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 with no filler, and the identifying information (Search Console OAuth connection) is front-loaded ahead of the qualifiers.

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 (no params, no nesting), but there is no output schema, so the description is the only place where return semantics could be stated — and it doesn't say what "configured" resolves to (boolean, credential metadata, error on missing config). Adequate to call correctly, incomplete for interpreting the result.

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 zero parameters, so the baseline is 4. There is nothing for the description to disambiguate, and it correctly avoids inventing parameter detail.

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 verb ("Check whether") and a specific resource ("the local read-only Search Console OAuth connection is configured"), which clearly separates it from the ads_auth_status, ga4_auth_status and gtm_auth_status siblings by naming the Search Console product. It stops short of explicitly routing the agent away from those siblings, but the resource naming does the differentiation work.

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?

There is no statement of when to call this tool, no prerequisite context (e.g. "call before search_console_list_sites"), and no guidance on what to do when the result is negative. The only usage signal is implied by the name itself.

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