Skip to main content
Glama

Connect Google Search Console

connect_search_console

Use this when the user wants to connect (or reconnect) Google Search Console for a site — typically right after get_search_console reported connected:false. Returns a consent_url: give it to the user as a link and ask them to open it and approve access with the Google account that owns the domain in Search Console. That one approval MUST happen in a browser — Google does not allow it any other way, so never claim you can do it for them. Nothing else is needed afterwards: the Search Console property is bound to the site's custom domain automatically, and get_search_console starts answering. If requires_custom_domain is true the site has no custom domain yet: connecting Google would grant access to nothing, so connect a domain first (connect_domain) and publish. Already connected? It returns a consent_url too, but hand that over ONLY to switch Google account; otherwise just read the numbers.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "app_id": "<app_id>",
      "context": "<context>"
    },
    "name": "connect_search_console"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYesThe app id to connect Search Console for
contextYesWhy this call, in one short sentence. Used to improve the connector; never include credentials or personal data.

Output Schema

NameRequiredDescriptionDefault
app_idNo
messageNo
site_urlNo
connectedNo
consent_urlNo
google_emailNo
custom_domainNo
site_selectedNo
expires_in_minutesNo
requires_custom_domainNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Well beyond the annotations: it discloses the return payload (consent_url), the hard constraint that approval MUST happen in a browser and cannot be done by the agent, the fact that no follow-up step is needed because the property binds to the custom domain automatically, and the failure mode when no custom domain exists. Nothing here contradicts readOnlyHint=false / destructiveHint=false / openWorldHint=false — the action is a state-changing but non-destructive binding.

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?

Front-loaded with the trigger, then the primary output, then the constraint, then the edge cases — a sensible information order with no filler. It is on the long side and the 'that one approval MUST happen in a browser' passage is emphatic rather than efficient, but each clause carries an operational instruction.

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?

For a 2-parameter connector mutation with an output schema, the description covers everything an agent needs: when to call, what comes back, what the human must do, what happens after, and both failure/precondition branches. Return-value explanation beyond consent_url is unnecessary given the output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for both parameters, so app_id and context are already documented in structured data. The description adds no syntax or semantics for either (it doesn't say where app_id comes from or what 'context' should contain), which is the expected baseline-3 case when the schema carries the load.

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?

States a specific verb and resource ('connect (or reconnect) Google Search Console for a site') and immediately situates it relative to siblings — it is what you call after get_search_console reports connected:false, and it is distinct from connect_domain. An agent can place it in the workflow 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?

Explicit trigger ('when the user wants to connect or reconnect'), explicit prerequisite handling ('if requires_custom_domain is true ... connect a domain first (connect_domain) and publish'), and an explicit exclusion for the already-connected case ('hand that over ONLY to switch Google account; otherwise just read the numbers'). Alternatives and when-not-to-use are both named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.