Skip to main content
Glama
Mrshahidali420

Google Search Console MCP Server

gsc_detect_browsers

Lists installed Chromium browser profiles and recommends one to use with the Google Search Console extension, based on local browser state without network calls.

Instructions

List the Chromium browser profiles on this machine and recommend one.

Local-only: reads the browsers' own state files, makes no network call, spends no quota, and needs no token — safe to call before signing in. Answers "which browser profile should I drive?", nothing else; it opens no browser and changes no setting.

PRIVACY: no email address is returned, in either direction. Not the account signed in to a profile, not the account that authorised this server, and not a profile display name that is itself an address. No filesystem path is returned either — a profile path carries the operator's account name. What identifies a profile here is its browser and its profile directory.

Returns {"ok": True, "profiles": [...], "recommended": <one of them or None>, "reasons": [...]}. profiles is a FLAT list across every browser, ranked-flag included, not grouped by browser — the question is which single profile to use, so each entry carries its own brand context (browser, browser_key, extensions_url) and stands alone. Each profile is {"browser", "browser_key", "extensions_url", "profile", "display_name", "account_on_disk", "account_discoverable", "matches_authorised_account", "has_extension", "recommended"}.

extensions_url is where that browser's extensions page lives (chrome://extensions, brave://extensions, ...). Use the value given; do not build one from the browser key, since Chromium registers no chromium:// scheme and uses chrome://extensions.

has_extension is TRI-STATE: true means the pairing extension is installed in that profile, false means every preferences file was read and it was not among them, and null means the check could not be PERFORMED — an unreadable preferences file, or no unpacked extension directory to match against. Read null as "not detected", never as "not installed"; telling a user with a working install to reinstall it is the one wrong answer this flag exists to avoid.

account_on_disk says an account address was found in that profile's files — found, not validated: no token is checked and nobody's live session is inspected, and on Microsoft Edge the same file records Microsoft accounts, so treat it as a hint rather than a login check. account_discoverable is a fact about the BRAND: Brave, Vivaldi, Opera and plain Chromium record no Google account at all, so account_on_disk: false there means "not discoverable", NOT "nobody is signed in". matches_authorised_account is true, false, or NULL — null means the question could not be asked (nothing has authorised yet, or the brand records nothing), and must not be read as "no". reasons explains the recommendation in plain sentences.

A machine with no Chromium browser installed returns ok: true with an empty profiles list, recommended: null, and a note saying what to install; that is an ordinary state, not a failure. Only an unexpected fault returns {"ok": False, "error": "unexpected", "detail": <exception type>, "fix": ...}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses local-only operation, no network/quota/token usage, no filesystem paths returned, privacy guarantees about email addresses, and the exact meaning of tri-state flags (has_extension, matches_authorised_account). It also explains error states. This exceeds typical expectations.

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?

The description is long but front-loaded with a one-sentence summary and purpose. Each paragraph adds essential caveats (privacy, tri-state semantics, edge cases). While not terse, every section is necessary given the tool's complexity, so it earns its length without being bloated.

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?

With no output schema, the description must document the return structure, and it does so exhaustively: the flat list format, each field's meaning, tri-state behavior, empty-list case, and error format. It also explains the 'recommended' field and reasons. This makes the description fully self-contained.

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 input schema has zero parameters, so there are no parameter semantics to explain. Per the rubric, a baseline of 4 is appropriate because there is nothing to add; the description focuses on output semantics 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 opening sentence 'List the Chromium browser profiles on this machine and recommend one' clearly states the action and scope. It also explicitly distinguishes itself by saying 'Answers "which browser profile should I drive?", nothing else', setting it apart from sibling tools like gsc_use_browser.

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?

The description states when it is safe to call ('safe to call before signing in') and defines its boundary relative to other tools ('opens no browser and changes no setting'). It does not explicitly name alternative tools, but the context signals (sibling gsc_use_browser) make the guidance clear.

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