Skip to main content
Glama

analyze_url

Analyze web pages to measure screen-reader navigation cost. Identify barriers preventing assistive-technology users from discovering, reaching, and operating interactive targets. Returns scored findings to guide accessibility fixes.

Instructions

Analyze a web page for screen-reader navigation cost. Returns scored findings showing how hard it is for AT users to discover, reach, and operate interactive targets. Read-only — navigates to the URL in a sandboxed browser but does not modify the page.

Recommended: Use format='sarif' for concise, actionable output (~4KB). SARIF auto-filters to findings that need attention (moderate and worse). JSON/markdown include every target and can be 100x larger.

SPAs (React, Next.js, etc.): Pass waitForSelector (e.g., '[data-testid="app"]' or 'main') so Tactual waits for the app to hydrate before capturing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to analyze
profileNoAT profile ID (generic-mobile-web-sr-v0, nvda-desktop-v0, jaws-desktop-v0, voiceover-ios-v0, talkback-android-v0)generic-mobile-web-sr-v0
deviceNoPlaywright device name for emulation (e.g., 'iPhone 14')
exploreNoExplore hidden branches (menus, tabs, dialogs). Use with format='sarif' to avoid output overflow.
formatNoOutput format. 'sarif' (recommended) filters to actionable findings only. 'json' includes all targets.sarif
minSeverityNoOnly include findings at this severity or worse. Reduces output size.
waitForSelectorNoCSS selector to wait for before capturing (essential for SPAs). E.g., 'main', '#app', '[data-hydrated]'
waitTimeNoAdditional milliseconds to wait after page load (default: 0). Use for slow-rendering SPAs.
timeoutNoPage load timeout in milliseconds
focusNoOnly analyze targets within these landmarks (e.g., ['main', 'navigation']). Reduces noise in large pages.
excludeSelectorNoCSS selectors to hide from analysis (e.g., ['#notifications', '.cookie-banner']). Elements are set aria-hidden before capture.
excludeNoGlob patterns to exclude targets by name/role/kind (e.g., ['*cookie*', '*notification*', 'banner']). Case-insensitive, supports * and ? wildcards.
maxFindingsNoMaximum detailed findings to return (default: 15 for JSON/markdown, 25 for SARIF). Use 3-5 for quick checks, higher for thorough audits.
probeNoRun keyboard probes on interactive targets (focus, activation, Escape recovery, Tab trapping). Adds ~30-60s but detects real focus management issues. Off by default — use for deep investigation, not for triage or fix-verify loops. analyze_pages never probes.
summaryOnlyNoReturn only summary stats (severity counts, top issue groups, average score) without individual findings. ~500 bytes. Use for quick page health checks before diving deeper.
includeStatesNoInclude captured states in JSON output for passing to trace_path's statesJson parameter. Uses compact format (~5KB): state IDs, target IDs+selectors+roles, and provenance. The 'states' key in the output is the value to pass as statesJson to trace_path.
storageStateNoPath to a Playwright storageState JSON file containing cookies and localStorage. Use save_auth to create this file, then pass the path here to analyze authenticated pages. Example: 'tactual-auth.json'
Behavior5/5

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

No annotations provided, but description carries full burden excellently: discloses 'sandboxed browser', 'does not modify the page', performance characteristics ('~30-60s', '~4KB', '~500 bytes'), filtering behavior ('auto-filters to findings that need attention'), and hydration waiting for SPAs. Rich behavioral context beyond safety hints.

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 paragraphs with zero waste: first states purpose+safety, second gives format recommendation with size rationale, third gives SPA-specific guidance. Markdown bolding highlights actionable sections. Every sentence provides unique value not present in structured fields.

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 complex 17-parameter tool with no output schema, the description effectively covers critical usage patterns (SPA hydration, authentication workflow, output format selection, probe vs no-probe). Deduct one point because it doesn't explicitly define 'AT' (assistive technology) and leaves some advanced parameters (focus, excludeSelector) to schema alone, though schema coverage is complete.

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 has 100% description coverage (baseline 3), but description adds significant semantic value: explains format selection trade-offs, waitForSelector hydration purpose, probe timing cost, includeStates integration with trace_path, and storageState workflow with save_auth. Elevates beyond schema with usage intent and integration context.

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?

Description uses specific verb 'Analyze' with clear resource 'web page' and scope 'screen-reader navigation cost'. The singular 'web page' implicitly distinguishes from sibling 'analyze_pages' (batch), and the probe parameter description explicitly notes 'analyze_pages never probes', reinforcing the distinction.

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?

Provides explicit recommendations: format='sarif' for concise output vs JSON/markdown '100x larger'; waitForSelector for SPAs; probe for 'deep investigation, not for triage'; storageState workflow referencing 'save_auth' sibling; summaryOnly for 'quick page health checks'. Clear when-to-use guidance for each major parameter.

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/tactual-dev/tactual'

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