Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Inspect URLs in Google Search Console

seo_inspect_urls
Read-onlyIdempotent

Read Google Search Console's existing index status for up to 10 URLs of the connected property: index/coverage state, last crawl time, Google-selected vs declared canonical, and mobile/rich-results verdicts. Use it to answer 'is this page indexed? why not?'. Google requires each URL to belong to that property. This does not run a live crawl. Per-URL failures are reported inline. Reads only the Search Console property already connected to an Sextant project the caller is authorized to access. The server selects the Google account and property from that project's saved connection. Read-only; uses no credits. It calls one fixed endpoint of the Sextant SEO API (https://sextantweb.com/docs/ai): urls are web page addresses.

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>",
      "urls": "<urls>"
    },
    "name": "seo_inspect_urls"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYes1–10 absolute URLs to inspect. Each must belong to the connected property.
siteIdYesThe Sextant site ID.
languageCodeNoBCP-47 language for the inspection result (e.g. 'en-US').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), it discloses that per-URL failures are reported inline rather than aborting the call, that no live crawl occurs, that no credits are consumed, and that the Google account and property are resolved server-side from the project connection. These are exactly the operational traits an agent needs and none appear in the annotation set.

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 scope are front-loaded in the first sentence, with exclusions and preconditions following in a logical order. The trailing sentence about the fixed endpoint and the appended 'urls are web page addresses' add little and read as bolted-on boilerplate.

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?

With no output schema, the description helpfully enumerates the returned fields and covers auth/connection sourcing, failure behavior, and the no-crawl caveat — enough to call the tool confidently. The only unresolved gap is how the required siteId relates to the property the server selects from the project connection.

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 coverage is 100% and already documents the 1–10 URL bound, URI format, property membership, and languageCode. The description only re-states the URL count/membership rule and adds the trivial note that 'urls are web page addresses', so it neither compensates for nor extends schema meaning. One mild tension remains: it says the server picks the property from the connection while siteId is still required, leaving that relationship unexplained.

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 (read) and resource (Google Search Console index status) with a bounded scope of up to 10 URLs, and enumerates the returned signals (coverage state, last crawl time, canonical selection, mobile/rich-results verdicts). It also explicitly rules out a neighboring behavior ('This does not run a live crawl'), separating it from crawl-based or performance-oriented siblings.

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?

Gives a concrete decision cue — 'Use it to answer is this page indexed? why not?' — plus a negative condition (no live crawl) and a precondition (URLs must belong to the property). It stops short of naming an alternative tool for the performance or site-listing cases, so routing guidance is clear but not exhaustive.

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