Skip to main content
Glama

MeshArc

by dev.mesharc
OverviewDiscussionsAdmin

List a run's pages

list_pages
Read-onlyIdempotent

List the pages one project run stored -- the last finished run unless run_id is given -- with each page's url, status, depth, word count and when it last changed, up to 500 rows, plus the runId. Use it to see what a crawl covered or to pick a URL; get_page reads one of them in full, search_pages finds pages by their text, and get_changes lists only what changed. Free and reads only what is stored: it never fetches the site. A project with no finished run answers with no pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
run_idNoA run's id, from start_run or the runId a list_pages answer carries; leave empty for the last finished run.
project_idYesThe project's id, as list_projects or create_project returns it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / project_id / description
      Added value: +"The project's id, as list_projects or create_project returns it."
    • addedInput schema / properties / run_id / description
      Added value: +"A run's id, from start_run or the runId a list_pages answer carries; leave empty for the last finished run."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: it is 'Free', it 'reads only what is stored: it never fetches the site', and it caps results at 500 rows. It stops short of describing ordering or truncation behavior beyond the row cap.

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 core action and scope, and every clause earns its place (fields returned, row cap, alternatives, edge case). The opening sentence is long and packs the returned-field list and default-run rule together, which costs a little readability.

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?

There is no output schema, and the description compensates by enumerating the returned fields (url, status, depth, word count, last changed, runId) and the 500-row cap. Combined with the default-run resolution and the no-pages edge case, an agent has everything needed to call it 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 run_id and project_id are already documented, including the 'leave empty for last finished run' default. The description restates the default resolution but adds no format or reference detail beyond the schema, so baseline 3 applies.

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 and resource (lists the pages a run stored) and immediately scopes it ('the last finished run unless run_id is given'). It also names the sibling alternatives (get_page, search_pages, get_changes) so the agent can tell it apart without opening other schemas.

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?

Explicit when-to-use ('see what a crawl covered or to pick a URL') and explicit routing to alternatives with the condition that selects each: get_page for full content, search_pages for text lookup, get_changes for diffs only. Also states the empty-project edge case ('no finished run answers with no pages').

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

All MeshArc 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