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

@mgcrea/mcp-google-search-console

by mgcrea

Search Console: Login

gsc_auth_login
Idempotent

Sign in with a Google account to authorize Search Console access, storing a refresh token and confirming which account's properties can be read.

Instructions

Sign in with Google: opens the consent screen in the browser and waits for it to finish, then stores a refresh token (mode 600) and reports the signed-in account. Pick the Google account that has access to the Search Console properties you want — the account, not any argument, decides which properties are readable. The app is unverified, so Google shows a warning first: Advanced → Go to (app). If no browser can be opened, or the wait runs out, returns the authorize URL instead and keeps listening for 5 minutes; call gsc_auth_status afterwards. Logging in again replaces the stored login.

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_login"
  }
}

Input Schema

NameRequiredDescriptionDefault
openNoOpen the consent screen in the default browser. false only returns the URL.
wait_secondsNoHow long to wait for the consent to complete before returning the URL instead. Defaults to 120.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the flow is interactive and blocking (opens consent and waits), that a refresh token is persisted with mode 600, that the OAuth app is unverified and triggers a Google warning with the exact click path, and that timeout returns the authorize URL while continuing to listen for 5 minutes. The destructive side effect of re-login ('replaces the stored login') is also stated, which the annotations alone would not convey.

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?

It is front-loaded with the action and effects, then the account-selection caveat and the fallback/failure path in priority order. It is somewhat dense across three long sentences, but each carries distinct operational information rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description covers all relevant return shapes: a stored token plus signed-in account on success, or an authorize URL on timeout/no-browser. For an interactive auth tool, the prerequisites, side effects, and recovery path are all present.

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?

Schema coverage is 100%, so the baseline is 3; the description adds meaning by clarifying that no argument selects the Search Console account — the chosen Google account alone determines property visibility — and by explaining the wait/return-URL tradeoff that wait_seconds controls. It does not restate parameter syntax, which is appropriate since the schema already does.

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 opens with a concrete verb and resource ('Sign in with Google'), then states the observable effects: consent screen, stored refresh token, reported account. It is clearly distinguished from gsc_auth_status, which is named as the follow-up tool in the fallback case.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It gives actionable selection guidance ('pick the Google account that has access to the properties you want') and a conditional path ('if no browser can be opened, or the wait runs out ... call gsc_auth_status afterwards'), plus the re-login behavior. It stops short of stating when not to use it (e.g., use gsc_auth_status to check an existing login instead of re-authenticating), so it is not fully exhaustive.

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