Skip to main content
Glama

Site heading outline

site_heading_outline
Read-only

Pro. Check heading structure across a site. Crawls the site from url (same origin only, up to 40 pages, 4 requests at a time, or only the paths you list), uses sitemap.xml to find pages, and obeys robots.txt for the user agent ATPDesigners. Reads static HTML only. The result opens with coverage: pages read of pages found, which were skipped or truncated, and requests used. Returns each page's heading outline, pages with no h1 or more than one, skipped levels, empty headings, duplicate titles and h1s, and a site-wide table.

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": {
      "url": "<url>"
    },
    "name": "site_heading_outline"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesHome page or any page on the site. The crawl stays on this origin.
pathsNoOptional list of same-origin paths such as /about. When given, only these pages are read and links are not followed.
sitemapNoUse sitemap.xml to find pages. Default true.
maxPagesNoOptional lower page cap. The hard cap is 40 pages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: same-origin restriction, 40-page hard cap, 4 concurrent requests, robots.txt compliance for a named user agent, static-HTML-only (no JS rendering), sitemap discovery, and what the output's coverage preamble contains. That is exactly the operational context an agent needs before calling a crawler.

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 purpose is front-loaded in the first sentence and the remaining two sentences are dense with non-redundant specifics. Slight deduction for the cryptic 'Pro.' prefix (unexplained tier label) and the long comma-chained middle sentence that packs limits together.

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 carries the return-value burden and does it well: coverage counters, skipped/truncated pages, heading outlines, and the specific defect classes reported (missing/multiple h1, skipped levels, empty headings, duplicate titles). Only error/failure behavior and result size are left unaddressed.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds value: it clarifies that `paths` disables link-following versus the sitemap-driven crawl, and that `maxPages` is bounded by a hard 40-page cap. These behavioral interactions between parameters are not in the schema text.

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 first sentence names a specific verb and resource ('Check heading structure across a site'), and the following sentences add real scope detail (origin-restricted crawl, 40-page cap, sitemap, robots.txt). It is clearly distinguishable from most siblings, though it never names the closest alternatives such as sitemap_to_outline or content_hierarchy_check.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the agent can infer this is the site-wide heading audit tool from the behavior described. There is no explicit 'use this when…' statement, no exclusion against the similar heading/hierarchy siblings, and no prerequisite guidance beyond the crawl mechanics.

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