Skip to main content
Glama

Get audit issues

get-audit-issues
Read-only

Get site audit issues, highest impact first, with title, severity, category, impact_score and issue_fingerprint (what update-issue-status takes). Pass audit_id (from list-site-audits) for one audit, or domain_id to get the issues from every audit of the domain completed after since (default the last 24 hours), each with its audit_id, completed_at and page url. min_severity keeps that severity and above. get-site-health-summary counts issues across audits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get-audit-issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 50
sinceNoWith domain_id: audits completed after this ISO time, default 24 hours ago
audit_idNoAudit ID from list-site-audits
categoryNoFilter by category
severityNoOnly this severity
domain_idNoDomain ID from list-domains, instead of audit_id
min_severityNoThis severity and above

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / domain_id
      Added value: +{
      +  "description": "Domain ID from list-domains, instead of audit_id",
      +  "format": "uuid",
      +  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +  "type": "string"
      +}
    • addedInput schema / properties / min_severity
      Added value: +{
      +  "description": "This severity and above",
      +  "enum": [
      +    "critical",
      +    "high",
      +    "medium",
      +    "low"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / severity / description
      Previous value: -"Filter by severity"New value: +"Only this severity"
    • addedInput schema / properties / since
      Added value: +{
      +  "description": "With domain_id: audits completed after this ISO time, default 24 hours ago",
      +  "format": "date-time",
      +  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "audit_id"
      -]
  2. Changed2 schema fields changed
    • changedInput schema / properties / audit_id / description
      Previous value: -"Audit ID"New value: +"Audit ID from list-site-audits"
    • changedInput schema / properties / limit / description
      Previous value: -"Max results"New value: +"Max results, default 50"
  3. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / audit_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds real behavioral context beyond that: result ordering by impact, the field set returned, and the implicit 24-hour default window when domain_id is used. It does not mention truncation/pagination behavior beyond the limit cap, which is the only notable gap.

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 resource name, ordering, and returned fields, and every clause carries information rather than padding. It is, however, written as two very long run-on sentences with heavy parenthetical nesting, which slightly hurts scannability for an agent parsing it.

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?

With seven optional parameters, no output schema, and a dual audit_id/domain_id mode, the description supplies what the structured fields cannot: returned fields, ordering, the default time window, and the relationship to update-issue-status. It is complete enough to call correctly, with only pagination/truncation semantics left implicit.

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 default baseline is 3, but the description adds genuine meaning: provenance for audit_id ('from list-site-audits') and domain_id, the fact that 'since' only applies in the domain_id path, and that min_severity is inclusive of that severity and above. It omits any detail on limit behavior, but the schema already documents its default and maximum.

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 (get site audit issues) plus the ordering ('highest impact first') and the exact fields returned (title, severity, category, impact_score, issue_fingerprint). It also explicitly contrasts itself with a sibling by noting that get-site-health-summary counts issues across audits, so an agent can distinguish the two 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 explicit branching guidance: pass audit_id for a single audit, or domain_id to pull issues from every audit of the domain completed after 'since' (default 24 hours). It also documents the min_severity vs severity filter distinction and points to update-issue-status as the consumer of issue_fingerprint, so the downstream workflow is 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