Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Google Search Console setup

google_setup_status
Read-onlyIdempotent

Where the site's Google Search Console setup stands: connected Google accounts, the property in use, whether Search Console has a property for the domain, where the domain's DNS is managed, and the next step with links. Start here when someone wants Google search data or does not see their site in Search Console.

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": {
      "siteId": "<siteId>"
    },
    "name": "google_setup_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. Beyond that, the description usefully discloses the contents of the response, including actionable "next step with links", which is real added context. It does not mention auth or connection prerequisites beyond the presence of connected accounts.

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?

Purpose and returned fields are front-loaded in the first sentence, with the usage cue immediately following. The field enumeration is dense but each item earns its place; slightly long but no 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?

For a read-only, single-parameter status tool with no output schema, the description fully covers what the agent will learn and when to reach for it. The only omission, siteId format, is minor against an otherwise complete picture.

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 coverage is 0% and the single required siteId parameter is never explained. The phrase "the site's ... setup" implies site scoping but does not clarify the expected identifier format or where to obtain it, leaving the schema to speak entirely for itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete resource (the site's Google Search Console setup) and enumerates exactly what the snapshot covers: connected accounts, the property in use, whether a property exists for the domain, DNS management location, and next steps. An agent can tell this apart from performance or listing tools, though it stops short of naming a sibling explicitly.

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?

"Start here when someone wants Google search data or does not see their site in Search Console" gives clear entry-point guidance and a diagnostic trigger. It does not state exclusions or point to the specific alternative (e.g., a Search Console performance tool) once setup is confirmed.

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.

Resources