Skip to main content
Glama

Get the heading outline of a web page (H1-H6 in document order) with counts per

headings
Read-only

Get the heading outline of a web page (H1-H6 in document order) with counts per level and structure warnings (no H1, several H1s, skipped levels). Fast (under 2 s). Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.001 per call (x402, USDC on Base).

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint, openWorldHint), and the description adds information they cannot: a performance bound (under 2 s), a free quota of 20 calls/day per user, and the paid tier at $0.001 per call via x402/USDC on Base. The main gap is that it doesn't say what failure looks like on non-HTML, blocked, or 4xx pages, but the cost/rate-limit disclosure is substantive beyond annotations.

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 capability and output shape, then performance, then billing — a sensible priority order. The pricing sentence is long relative to the core purpose, but it is genuinely required information for an agent operating under a quota, so it earns its place.

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 compensates by enumerating the return content (per-level counts, ordering, warning types), which is the key completeness need here. The paid-call flow is covered by the schema rather than the prose, and edge-case behavior on malformed or blocked pages is unstated — the only meaningful remaining gap.

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 both `url` and `payment` are already documented in the schema, including the base64 PAYMENT-SIGNATURE mechanics and the instruction to omit it on the first call. The description adds no parameter-level meaning beyond restating the pricing scheme, which is the correct baseline for a fully documented two-parameter schema.

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 opens with a specific verb and resource ('Get the heading outline of a web page') and immediately scopes it: H1-H6, document order, counts per level, plus named structure warnings (no H1, several H1s, skipped levels). This is a distinct capability that an agent can separate from siblings like page_markdown or seo_audit without opening the schema.

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?

Useful context is given implicitly by the mention of structure warnings, which tells the agent this is the tool for heading-hierarchy audits rather than raw text extraction. However, no sibling is named as an alternative and there is no when-not-to-use guidance (e.g. for non-HTML or authenticated pages).

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.