Skip to main content
Glama

Scan a URL for accessibility issues

scan_url

Run an axe-core accessibility audit on any URL, detecting WCAG violations and providing fix guidance for live pages or local servers.

Instructions

Loads a URL in headless Chromium, runs an axe-core accessibility audit, and returns WCAG violations with fix guidance. Use for live pages (http/https) or local dev servers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to scan (http:// or https://).
tagsNoWCAG / rule tags to run, e.g. ["wcag2a","wcag2aa","wcag21aa","best-practice"]. Omit to run the default rule set.
rulesNoOnly run these axe rule ids, e.g. ["color-contrast","image-alt"].
detailNo"summary" lists violated rules and counts only; "full" (default) also lists offending elements and fix guidance.full
includeNoOptional CSS selector to scope the scan to one region of the page.
maxNodesNoMax offending elements to list per rule when detail=full.
timeoutMsNoNavigation timeout in milliseconds (default 30000).
excludeRulesNoAxe rule ids to skip.
includeIncompleteNoAlso report axe "incomplete" items — checks that need manual review (e.g. color-contrast over images, aria-hidden focus). Off by default; set true to surface likely issues automated rules could not confirm.
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses loading in headless Chromium and running axe-core, but does not mention side effects (likely read-only), permissions, or security considerations. Behavior is adequately, not thoroughly, described.

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 concise: two sentences with no wasted words. It front-loads the primary action and context, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description lacks details about return value structure (e.g., output schema), error handling, or pagination. With no output schema, a more complete description of the response format would be beneficial. For a tool with 9 parameters and no output schema, the description is not fully complete.

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%, with all parameters described in the schema. The description adds no additional parameter semantics beyond the schema. Baseline of 3 is appropriate as the schema already provides sufficient detail.

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 clearly states the tool's action: scanning a URL for accessibility issues using axe-core. It specifies the target (live pages or local dev servers), distinguishing it from sibling tools like scan_file or scan_html.

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 provides clear context for use: 'Use for live pages (http/https) or local dev servers.' It implicitly excludes non-live content (files, HTML strings, site maps), but does not explicitly mention when not to use it or name alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Ravindrabisht12/axe-devtool-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server