Skip to main content
Glama

The pages of a website scan

list_website_pages
Read-onlyIdempotent

Page inventory of a scan: address, status, images, sizes, estimated and measured savings. Paged; filter by status or search. Reads only.

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": {
      "scan_id": "<scan_id>"
    },
    "name": "list_website_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 50.
offsetNo
searchNoPart of the address or title.
statusNo
scan_idYesThe scan's id, from list_website_scans or the web app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so 'Reads only' is largely redundant. The description does add real behavioral value with 'Paged', signalling that results are paginated, and it discloses the returned metrics (estimated and measured savings), but says nothing about page-size defaults, total counts, or whether paging is offset-based.

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 resource and its payload, then pagination/filtering, then the read-only note — a sensible information order with no filler. Slightly telegraphic field lists and the redundant 'Reads only' clause keep it off a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five parameters and no output schema, the description usefully enumerates the returned fields, which is its main compensating job. However, it leaves pagination mechanics (does the response include a total or next offset?) and the distinction from asset/report siblings unaddressed, so an agent still has gaps before calling it.

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 60%: limit, search and scan_id are already documented in the schema (including a pointer to list_website_scans for the id). The description adds only that 'status' and 'search' act as filters, while offset and the status enum values remain undocumented in prose. Baseline 3 is appropriate since the schema does most of the work.

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 specific resource ('Page inventory of a scan') and enumerates the fields returned (address, status, images, sizes, savings), which distinguishes it clearly from list_website_scans and list_website_assets. It does not explicitly name those siblings as alternatives, but the noun 'pages of a scan' is specific enough to route an agent correctly.

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?

'Paged; filter by status or search' states how to narrow results, and 'Page inventory of a scan' implies it is the per-scan drill-down. There is no explicit when-to-use versus list_website_assets (which also surfaces images) or get_website_scan, so the agent must infer the boundary from names alone.

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