Skip to main content
Glama

MeshArc

by dev.mesharc
OverviewDiscussionsAdmin

Search a run's stored pages

search_pages
Read-onlyIdempotent

Find which pages of a project run contain some text or an element -- the last finished run unless run_id is given -- returning the matching URLs with how many pages were scanned. Use it to locate pages by what they say or contain; list_pages lists every page and get_page then reads one in full. It scans the stored copies and never fetches the site, so it is free and as fresh as the run. A selector search needs the run to have kept html (the rawHtml format); when none was kept the answer says so rather than reporting no matches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesWhat to look for, 1 to 200 characters. In content mode every word must appear and "quoted phrases" match as written; in selector mode a CSS selector, or an XPath starting with / or (.
modeNo'content' (default) searches the extracted markdown; 'selector' searches the stored html.content
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. Changed5 schema fields changed
    • addedInput schema / properties / mode / description
      Added value: +"'content' (default) searches the extracted markdown; 'selector' searches the stored html."
    • addedInput schema / properties / mode / enum
      Added value: +[
+  "content",
+  "selector"
+]
    • addedInput schema / properties / project_id / description
      Added value: +"The project's id, as list_projects or create_project returns it."
    • addedInput schema / properties / q / description
      Added value: +"What to look for, 1 to 200 characters. In content mode every word must appear and \"quoted phrases\" match as written; in selector mode a CSS selector, or an XPath starting with / or (."
    • 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.9/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavior: it scans stored copies rather than fetching the site, so it is free and only as fresh as the run. It also discloses the rawHtml/selector precondition and that a missing-html situation is reported explicitly rather than as zero matches.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the core purpose and then the disambiguation and the freshness/precondition caveats. No filler or repetition of what the schema or annotations already declare.

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?

With no output schema, the description still characterizes the result (matching URLs plus pages scanned) and the degenerate case where html was not retained. Combined with full parameter coverage and annotations, an agent has everything needed to invoke it correctly.

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 cross-parameter semantics the schema does not: selector mode depends on the run having preserved rawHtml, and run_id defaults to the last finished run. The quoted-phrase and CSS/XPath syntax details remain schema territory.

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 ('find which pages of a project run contain some text or an element') plus the return shape (matching URLs and scan count). It explicitly distinguishes itself from the siblings list_pages and get_page, so an agent can route without opening a 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 an explicit use case ('locate pages by what they say or contain') and names the two alternatives with their roles: list_pages lists every page, get_page reads one in full. It also states the default run scoping (last finished run unless run_id is given), so the when-to-use decision is fully specified.

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