Skip to main content
Glama

list_audits

List security audits run on your domains, newest first.

Every argument is optional. domain matches domains whose name contains
the given text. date_from and date_to (each a calendar date) bound the
range an audit was started in, inclusive of both ends. source is how
the audit was started: "on_demand" for one requested directly, or
"autopilot" for one the account's automated schedule started.
audit_status is the audit's current stage: "new", "in_progress",
"done", or "error". result is its overall verdict once finished:
"green", "yellow", or "red". limit caps how many audits are returned in
one call (default 20, maximum 100). cursor requests the next page and
is the nextCursor value a previous call to this tool returned — omit it
for the first page.

Returns a page of audit summaries — each with the audit's id, when it
started, the domain it ran against, its status, result and numeric
score — plus nextCursor, which is present when another page follows and
absent on the last page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
cursorNo
domainNo
resultNo
sourceNo
date_toNo
date_fromNo
audit_statusNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so thoroughly. It discloses ordering (newest first), filter semantics (contains, inclusive date ranges), pagination behavior (cursor from previous call, nextCursor absent on last page), and the exact fields returned per audit.

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?

The description is efficiently organized: one purpose sentence, one sentence per parameter group, and a return summary. Every sentence adds necessary information, especially given the 0% schema description coverage. It is front-loaded with the core purpose before diving into details.

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?

The description is complete for a read-only listing tool with 8 optional parameters. It covers filtering, pagination, output fields, and the terminal-page sentinel. Given the output schema exists and the description already explains the return shape, nothing essential is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain every parameter, and it does. Each of the 8 parameters gets a clear semantic explanation including enum meanings, inclusive date behavior, default/maximum limit, and how cursor pagination works.

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?

The description starts with a specific verb and resource: 'List security audits run on your domains, newest first.' This clearly differentiates it from siblings like get_audit (single audit) and start_audit (create an audit). The plural 'list' and the domain scope make the tool's purpose unambiguous.

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?

The description gives strong context about when this tool is appropriate: listing audits with optional filtering and pagination. It does not explicitly name alternatives or state when not to use it, but the 'every argument is optional' framing and pagination details make the intended usage clear.

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