Skip to main content
Glama
Sign In
flin-google-search-console-mcp

flin-google-search-console-mcp

by flin-agency
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

connection_status

Read-onlyIdempotent

Reports local setup and running version without Google sign-in or API calls; shows auth_status unknown and live_access not_checked until list_sites verifies access.

Instructions

Report local setup and running version; never sign in, refresh tokens or call Google.

A saved token cannot prove that Google still accepts it: auth_status is unknown in that case, and live_access remains not_checked. Run list_sites explicitly to sign in if needed and check access; it may display private property names.

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

Input Schema

NameRequiredDescriptionDefault
accountNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.8

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, closed-world behavior. The description adds crucial operational context beyond annotations: no sign-in, no token refresh, no Google calls, and saved-token limitations such as auth_status being unknown and live_access remaining not_checked. This directly prevents an agent from misinterpreting the result as proof of live access.

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?

The description is short and front-loaded with the core purpose. The second paragraph adds only high-value caveats and the explicit alternative, with no wasted wording.

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?

For a read-only status tool with annotations and an output schema, the description covers the main behavioral caveats and the relevant alternative well. The one notable gap is that the optional account parameter is not explained anywhere.

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

Parameters2/5

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

Schema description coverage is 0%, so the description should compensate but does not. The sole optional account parameter is never mentioned, leaving its meaning and effect completely undocumented in both schema and description.

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 gives a specific verb and scope: report local setup and running version. It immediately distinguishes this from authentication or Google access by saying it never signs in, refreshes tokens, or calls Google. It also explicitly names list_sites as the alternative for access checks.

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 clearly states when to use this tool: local setup and version reporting only. It also states when not to rely on it for authentication, because a saved token cannot prove Google still accepts it. The alternative is explicit: Run list_sites to sign in if needed and check access.

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

Deploy Server

Other Tools