Skip to main content
Glama
Mrshahidali420

Google Search Console MCP Server

gsc_use_browser

Choose which browser profile the Google Search Console MCP server uses, overriding auto-detection. Pin a specific browser and profile, or clear the pin to return to the recommended option.

Instructions

Choose which browser profile this server drives, overriding detection.

Local-only: writes one preference to this server's config file, makes no network call, spends no quota, needs no token, and opens no browser. Use it when gsc_detect_browsers recommends a profile that is not the one holding your Search Console account — the detector can rank the profiles it finds, but it cannot know which browser you work in.

browser is the browser_key from gsc_detect_browsers ("chrome", "brave", "edge", "vivaldi", "opera", "chromium") — the key, not the display label. profile is the profile field from the same entry (the profile DIRECTORY, e.g. "Default" or "Profile 3"); omit it to take that browser's default profile. clear=True removes the pin and returns to the detector's recommendation, and ignores the other two.

The pair is checked against the profiles that actually exist BEFORE it is saved. A pair that matches nothing is refused with {"ok": False, "error": "browser_not_found", ...} whose fix lists the pairs that would work, so a typo is answered immediately rather than becoming a browser that silently never opens.

Once pinned, the choice is absolute: gsc_setup, gsc_doctor and every tool that drives the browser use it, and the ranking is not consulted. If the pinned profile later disappears — browser uninstalled, profile deleted — nothing falls back to a different one. Every affected tool stops and says the pin is dangling, because driving the wrong profile would submit URLs from whichever account happens to be signed in there.

The pin survives restarts. Returns {"ok": True, "pinned": "<browser> / <profile>" or null, "note": ...}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clearNo
browserNo
profileNo
Behavior5/5

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

No annotations, so description carries full burden. It discloses local-only writes, no network/quota/token, validation-before-save, absolute pin behavior, dangling-pin failure, and persistence. No contradictions.

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?

Front-loaded with one-line purpose, then structured paragraphs for constraints, usage, params, validation, and edge cases. Every sentence adds operational knowledge.

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?

Without output schema, it describes return shape and error response. Covers all parameters and non-happy-path behavior, making it complete for reliable invocation.

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

Parameters5/5

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

Schema has no descriptions, but description fully explains browser as key from gsc_detect_browsers, profile as directory string with omit behavior, and clear as override that ignores other params.

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 verb 'Choose' and resource 'browser profile', and explicitly frames as overriding detection. Distinguishes itself from gsc_detect_browsers by explaining it selects rather than detects.

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?

Explicitly tells when to use: when detection recommends a profile that doesn't hold the account. It also contrasts with gsc_detect_browsers, clarifying that detection can rank but cannot know user's browser.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Mrshahidali420/google-search-console-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server