Skip to main content
Glama
@mgcrea/mcp-google-search-console

@mgcrea/mcp-google-search-console

by mgcrea

Search Console: Auth Status

gsc_auth_status
Read-only

Check whether the Google Search Console server is configured and signed in, which account and properties it can access, and what setup steps to follow when a tool, property, or setting is missing.

Instructions

Whether the server is configured and signed in, which Google account the token belongs to (the account decides which properties exist at all), how many properties it can read, the granted scopes, whether the write tools are registered, and the quota model. When unconfigured, returns the exact setup steps. Call this first when a tool you expected is missing, a property is not found, or a setting seems to have no effect (config_issues lists values that were clamped or ignored).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuine context beyond that, notably that an unconfigured server returns exact setup steps and that `config_issues` surfaces clamped/ignored settings. It stops short of describing the response shape (field names, nesting) for most of the listed data, which is the remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler, and the diagnostic trigger is front-loaded in the second sentence. The first sentence is a long run-on enumeration of return fields, which is dense but each item earns its place as a reason to call the tool.

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?

With no output schema, the description carries the burden of explaining what comes back, and it largely does by listing the reported facts and the unconfigured-case behavior. What is missing is the concrete response structure (how these fields are named/nested), though the `config_issues` field is called out explicitly.

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 (schema coverage 100%), so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly adds no parameter talk and spends its space on diagnostic value instead.

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 names a specific resource (server auth/config state) and enumerates exactly what it reports: signed-in status, token's Google account, readable property count, granted scopes, whether write tools are registered, and the quota model. This is clearly a read-only status tool, distinguishable from siblings gsc_auth_login and gsc_auth_logout without opening 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 Guidelines5/5

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

It explicitly routes usage with diagnostic triggers: 'Call this first when a tool you expected is missing, a property is not found, or a setting seems to have no effect.' The condition under which `config_issues` matters (clamped or ignored values) is also stated, leaving little to inference.

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