Skip to main content
Glama

squirrelscan

by com.squirrelscan
OverviewDiscussionsAdmin

List audits

list_audits
Read-only

List the organization's audit runs: currently active (queued/pending/running; queued means waiting for a free cloud slot, and it starts by itself) plus recent runs of any status. Pass website_id (from list_websites) to get one website's full audit history, oldest runs included, and page through it with limit/offset using the returned total/has_more. This is the way to reach the preserved reports of a soft-deleted website: its runs still list under its old website_id. total/has_more describe the recent array only, and recent already includes any queued/pending/running run, so active is a live view of those same runs and not extra items to add to the count. Use the run ids with get_audit_status or get_report, and website ids with list_issues. Numbers on a recent run come from its published report (#1700): health_score is that report's overall score (the same value as get_report's summary.healthScore; null when the site was blocked or down, which earns no grade) and issues_found is the report's failing + warning checks (its summary.failed + summary.warnings). health_score is the metric to compare run over run: it is the only one rescored consistently across the whole site. Do NOT compare issues_found with the open count from list_issues: the issue tracker folds a rule failing on many pages into one open issue and carries issues forward until they are re-checked, so its count is legitimately much smaller and moves independently.

Input Schema

NameRequiredDescriptionDefault
limitNoMax recent runs to return (default 20, max 100).
offsetNoPagination offset into the recent runs (default 0). Use with total/has_more.
website_idNoOnly return runs of this website (id from list_websites, run_audit, or add_website). Works for soft-deleted websites too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +{}
  2. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
  3. Changed4 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max recent runs to return (default 20)."New value: +"Max recent runs to return (default 20, max 100)."
    • changedInput schema / properties / limit / maximum
      Previous value: -50New value: +100
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Pagination offset into the recent runs (default 0). Use with total/has_more.",
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / website_id
      Added value: +{
+  "description": "Only return runs of this website (id from list_websites, run_audit, or add_website). Works for soft-deleted websites too.",
+  "type": "string"
+}
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare a safe, non-destructive read, but the description adds behavior the annotations cannot convey: queued runs wait for a free cloud slot and start by themselves, total/has_more cover only the `recent` array, and preserved runs of soft-deleted websites remain reachable by their old website_id. This is substantial lifecycle and edge-case context.

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

Conciseness3/5

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

The purpose is front-loaded and most clauses carry weight, but the paragraph is a dense run-on that restates the recent-vs-active relationship twice (total/has_more describe recent only, and recent already includes active) and buries the metric semantics in a long final sentence. It is more verbose than it needs to be for a three-parameter list tool.

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, so the description must carry the return semantics, and it does: it defines the active/recent arrays, total/has_more, the source of health_score (#1700 report's overall score, null when blocked or down), and how issues_found is derived. An agent has everything needed to call and interpret it.

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 three parameters are already documented, setting a baseline of 3. The description adds real meaning on top: it ties website_id to list_websites as the source, notes it works for soft-deleted sites, and defines the limit/offset pagination contract in terms of the returned total/has_more.

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+resource (list the organization's audit runs) and immediately scopes it to active plus recent runs. It clearly distinguishes itself from siblings by naming get_audit_status, get_report, and list_issues as the tools for the downstream artifacts this list points at.

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 explicit when-to-use conditions: pass website_id for one site's full history, use limit/offset with total/has_more to page, use run ids with get_audit_status/get_report and website ids with list_issues. It also flags the soft-deleted-website case and an explicit 'do NOT compare issues_found with the open count from list_issues', which is a genuine anti-pattern warning.

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

All squirrelscan toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources