Skip to main content
Glama

Visibility Genies

Read audit issues

get_audit_issues
Read-only

Reads the findings of a site audit, most serious first, with a count per check, what each check means and how to fix it. Free: reads saved audit data. Findings and checks the project hid in Site Audit are left out, and the answer says how many. Omit auditId for the audit Site Audit shows.

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": "get_audit_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost issues to return (default 200).
auditIdNoAudit ID. Leave it out to use the audit Site Audit opens: the newest completed audit of the project's own site that read at least one page (until one exists, the latest audit of any kind).
severityNoOnly issues of this severity.
issueTypeNoOnly issues of one check. Known checks: blocked-page, rate-limited-page, crawl-rate-limited, crawl-forbidden-stop, crawl-challenge-stop, crawl-host-paused, site-unreadable, search-engine-blocked, robots-txt-unreadable, robots-txt-ignored, llms-txt-missing, llms-txt-unusable, llms-txt-found, robots-blocked-sitemap-url, robots-blocked-link, ai-crawler-blocked, client-rendered, javascript-site, sitemap-fallback-crawl, large-html, noindex-page, canonicalized-page, canonical-conflict, redirect-chain, redirect-loop, temporary-redirect, permanent-redirect, start-redirects-off-site, redirect-external, structured-data-invalid, structured-data-missing, open-graph-missing, hreflang-invalid-code, hreflang-missing-self, hreflang-not-reciprocated, server-error, broken-internal-link, missing-title, broken-page, duplicate-title, duplicate-meta-description, duplicate-content, missing-meta-description, missing-h1, multiple-h1, thin-content, images-missing-alt, orphan-page, no-outgoing-links, title-too-long, title-too-short, meta-description-too-long, meta-description-too-short, heading-order-skip, slow-response, slow-server, non-secure-page, mixed-content, mixed-content-blocked, url-too-long, url-underscores, url-too-many-parameters, broken-external-link, external-link-not-checked, nofollow-internal-link, single-inbound-link, link-no-anchor-text, link-non-descriptive-anchor, deep-page.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
metaNo
issuesYes
summaryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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: results are severity-ordered, hidden findings and checks are excluded, and the response reports how many were omitted. It does not mention pagination or result-size behavior, which is the remaining gap.

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 what is returned and in what order, then cost, then exclusions, then the auditId default. No filler and no repetition of schema detail beyond what aids selection.

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?

An output schema exists, so return values need not be spelled out, and the description still covers ordering, filtering defaults, hidden-item behavior and audit selection. For a read-only, five-parameter tool with full schema coverage, nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, including a full enum for issueType and a detailed auditId fallback rule, so the schema carries the parameter burden. The description's auditId note largely restates the schema's default-audit behavior rather than adding new meaning, so baseline 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 ('Reads the findings of a site audit') plus the ordering ('most serious first') and payload shape ('count per check, what each check means and how to fix it'). This is clearly distinguishable from get_audit_pages and get_audit_status, which cover pages and run state rather than findings.

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?

Gives concrete selection guidance for the key optional parameter ('Omit auditId for the audit Site Audit shows') and notes the call is free and reads saved data, implying no audit needs to be run first. It does not explicitly say when to prefer this over get_audit_pages or run_site_audit, so it stops short of full alternative routing.

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