Skip to main content
Glama

Site audit (crawl)

search_console_site_audit
Read-only

Crawls a verified Search Console site to identify indexing and click blockers: broken links, redirects, noindex sitemap pages, canonical conflicts, missing titles, orphan pages, and slow pages.

Instructions

Crawls a Search Console property's own website, politely and up to max_pages, and reports what holds back indexing and clicks: broken pages and the links to them, redirect chains, noindex or redirecting pages in the sitemap, canonical conflicts, missing or duplicate titles and descriptions, H1 problems, orphan pages nothing links to, pages missing from the sitemap, slow pages, and Google's index status for a sample. Only verified properties. Takes up to a minute. Changes nothing.

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": {
      "site_url": "<site_url>"
    },
    "name": "search_console_site_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost rows in each list
site_urlYesSearch Console property exactly as search_console_sites lists it, e.g. sc-domain:example.com or https://www.example.com/
max_pagesNoMost pages to fetch
index_sampleNoPages to check in Google's index (URL Inspection), likeliest problems first

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.46.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds real context on top: crawl politeness ('politely'), runtime ('up to a minute'), and the authorization prerequisite ('only verified properties'). It does not discuss truncation behavior when max_pages caps the crawl or how partial results are signaled, which keeps it below 5.

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?

Front-loaded with the verb and resource, then a single dense enumeration of findings, followed by the operational constraints. The long clause list is substantive rather than filler, though it makes the description read as one run-on sentence with no structural breaks.

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 carries the burden of conveying what comes back, and it enumerates the finding categories and index-status sampling thoroughly. Combined with the latency, authorization, and safety statements, an agent has everything needed to decide and invoke correctly.

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 description coverage is 100%, so all four parameters (limit, site_url, max_pages, index_sample) are already documented at the field level. The description only echoes max_pages ('up to max_pages') and adds no interpretation of limit or index_sample, so the schema is doing the heavy lifting.

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 (crawls) on a specific resource (a Search Console property's own website) and enumerates the exact finding classes it returns (broken links, redirect chains, noindex sitemap URLs, canonical conflicts, orphan pages, slow pages, index status). The scope difference from per-URL siblings like search_console_inspect_urls is evident without opening a schema.

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?

'Only verified properties' and 'Takes up to a minute' give clear preconditions and cost expectations, and the site-wide crawl framing implies it is the broad audit rather than a per-URL check. It never explicitly names an alternative such as search_console_inspect_urls for single-URL checks, so it stops short of full when/when-not routing.

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