Skip to main content
Glama

Visibility Genies

List site audits

list_audits
Read-only

Lists a project's site audits, newest first, with each audit's ID, start URL, status, pages crawled, crawler identity and dates. Pass an ID to get_audit_status, get_audit_issues or get_audit_pages to read an earlier audit. Free: reads saved audit data. Audits older than the history the plan keeps are left out.

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": {
      "projectId": "<projectId>"
    },
    "name": "list_audits"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost audits to return (default 20).
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
metaNo
totalYes
auditsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the low-risk profile is covered. The description adds genuinely non-structured behavior: newest-first ordering, the retention cutoff ('audits older than the history the plan keeps are left out'), and that the call has no cost because it reads stored data.

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?

Four sentences, front-loaded with purpose and return shape, then routing, then cost, then caveat. The telegraphic 'Free: reads saved audit data.' is slightly clipped but still information-dense with no filler.

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 a two-parameter read tool with a full schema, an output schema and safety annotations, the description covers purpose, ordering, drill-down routing, cost and data-retention limits. Only pagination behavior beyond the limit parameter is left implicit.

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 100% and the schema already documents projectId (with a pointer to list_projects) and limit (default 20, max 100). The description adds nothing about either parameter, so the baseline of 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 a project's site audits') plus ordering ('newest first') and the exact fields returned (ID, start URL, status, pages crawled, crawler identity, dates). An agent can distinguish this from run_site_audit and the get_audit_* family without opening any schema.

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

Usage Guidelines4/5

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

Explicitly routes drill-down to get_audit_status, get_audit_issues and get_audit_pages by passing an audit ID, which makes the list-then-fetch workflow clear. It does not explicitly contrast with run_site_audit (starting a new crawl), though 'reads saved audit data' strongly implies it, so guidance is clear but not exhaustive.

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