Skip to main content
Glama
Sign In

CiteLadder

by com.citeladder
OverviewDiscussionsAdmin

Read site pages

read_site_pages
Read-onlyIdempotent

Pages from a crawl, paged: URL, title, page type, status, scores, issue count and the rule ids of each page's issues by finding class. Pass url to find a page by its address, rule_id (from read_site_health top_issues or an issue group) to list exactly the pages affected by that issue, each with rule_evidence: what that check found on that page (a site-level architecture issue is recorded once on the home page, and its rule_evidence names the affected pages); filter by page_kind or status to find pages by type or status. This returns metadata, not page copy: use read_page_text for a page's words. read_site_health gives the totals.

Input Schema

NameRequiredDescriptionDefault
urlNoA page address or part of one, such as https://example.com/pricing or /pricing; keeps pages whose URL contains it, ignoring scheme, www and a trailing slash.
limitNoHow many rows to return; omit for the default page size.
cursorNoThe next_cursor a previous page returned.
statusNoKeep only pages in this state.
rule_idNoA Site Health rule_id; returns only the pages with a current issue of it.
crawl_idNoA crawl id that read_site_health returned; omit for the latest crawl.
page_kindNoKeep only pages of this type.
project_idYesA project id that list_projects returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / url
      Added value: +{
+  "description": "A page address or part of one, such as https://example.com/pricing or /pricing; keeps pages whose URL contains it, ignoring scheme, www and a trailing slash.",
+  "maxLength": 2048,
+  "minLength": 1,
+  "type": "string"
+}
  2. Changed4 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"How many rows to return; omit for the default page size."
    • addedInput schema / properties / page_kind / description
      Added value: +"Keep only pages of this type."
    • addedInput schema / properties / project_id / description
      Added value: +"A project id that list_projects returned."
    • addedInput schema / properties / status / description
      Added value: +"Keep only pages in this state."
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely useful behavior: output is metadata only, and the non-obvious rule that a site-level architecture issue is recorded once on the homepage with rule_evidence naming the affected pages. It does not spell out default page size or how cursor progression terminates, leaving modest gaps in the read loop.

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-loads the return payload, then the three filtering paths, then the two disambiguating pointers — a deliberate and readable order with no filler. It is dense (one long multi-clause sentence in the middle) and slightly hard to scan, but every clause carries information.

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?

For an 8-parameter filtered-list tool with no output schema, the description carries the return burden well by enumerating fields and explaining rule_evidence's indirect semantics. The only shortfall is paging mechanics, which the schema documents but the description never reinforces.

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 3 is the baseline, but the description adds meaning beyond the schema: rule_id provenance from read_site_health top_issues or an issue group, and what rule_evidence contains per page. It does not restate the url normalization or crawl_id defaulting rules, which the schema already handles.

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?

Opens with a specific verb and resource ("Pages from a crawl, paged") and immediately enumerates the returned fields, so the agent knows exactly what object it gets. It draws explicit boundaries against read_page_text ("metadata, not page copy") and read_site_health (totals), making it distinguishable from siblings without opening either schema.

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

Usage Guidelines5/5

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

Gives per-parameter routing rules: pass url to find a page by address, rule_id (sourced from read_site_health top_issues or an issue group) to list exactly the affected pages, page_kind or status to find pages by type or state. It also names the two alternatives and when to prefer them, leaving no inference required.

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

All CiteLadder toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources