Skip to main content
Glama

analyze_url

Measure screen-reader navigation cost on a web page. Returns scored findings showing how hard it is for assistive-technology users to discover, reach, and operate interactive targets.

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. Navigates to the URL in a sandboxed browser. Probes test keyboard behavior but do not submit forms or modify data.

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.
exploreDepthNoMax exploration depth (default: 2). How many levels of branches to walk when explore=true. Higher = more thorough, but each level multiplies action count. CLI defaults to 3 for power-user runs; MCP defaults to 2 for tighter agent-loop latency.
exploreBudgetNoMax total actions during exploration across all branches (default: 30). Prevents pathological pages from exploding probe time. CLI default is 50; MCP default is 30 for tighter agent-loop latency.
exploreTimeoutNoTotal exploration timeout in ms; includes initial/revealed probe time when probe is enabled (default: 60000).
exploreMaxTargetsNoMax accumulated targets before exploration stops early (default: 2000).
allowActionNoGlob patterns for controls that should be explorable despite the safety policy.
formatNoOutput format. 'sarif' (recommended) filters to actionable findings only.sarif
minSeverityNoOnly include findings at this severity or worse. Reduces output size.
waitForSelectorNoCSS selector to wait for before capturing (essential for SPAs).
waitTimeNoAdditional ms to wait after page load.
timeoutNoPage load timeout in ms
focusNoOnly analyze targets within these landmarks.
excludeSelectorNoCSS selectors to hide from analysis (set aria-hidden before capture).
scopeSelectorNoCSS selectors that define the subtree(s) to capture, score, and probe.
excludeNoGlob patterns to exclude targets by name/role/kind.
maxFindingsNoMaximum detailed findings to return.
probeNoRun keyboard probes on interactive targets. Adds ~30-60s.
probeBudgetNoMaximum number of targets for the generic probe. Overrides probeMode's generic budget.
probeModeNoProbe depth preset: fast=5/5/3/5, standard=20/20/10/20 (default), deep=50/40/20/40. Budgets are generic/menu/modal/widget.standard
probeSelectorNoCSS selectors that narrow probes without changing capture/scoring.
entrySelectorNoActivate this trigger before capture/probe, then prioritize newly revealed targets.
goalTargetNoExact-ish target id, name, role, kind, or selector hint for goal-directed probing.
goalPatternNoGlob pattern matched against target id/name/role/kind/selector for goal-directed probing.
probeStrategyNoProbe family intent preset. Default all; use overlay, form, composite-widget, navigation, modal-return-focus, or menu-pattern to spend budget on one class of behavior.
summaryOnlyNoReturn compact summary stats. Use for quick page health checks.
includeStatesNoInclude captured states in JSON output for passing to trace_path's statesJson parameter. Uses compact format (~5KB).
storageStateNoPath to Playwright storageState JSON (cookies + localStorage). Must be within cwd.
channelNoBrowser channel: chrome, chrome-beta, msedge. Bypasses shared pool.
stealthNoApply anti-bot-detection defaults. Pair with channel for Cloudflare-protected sites.
checkVisibilityNoRun the per-icon visibility probe across profile-declared (colorScheme × forcedColors) modes. Emits hcm-icon-invisible, low-contrast-icon, and hcm-substitution-risk findings. Undefined defers to the profile default (desktop AT profiles declare the full matrix; mobile/generic do not).
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 of disclosing behavioral traits. It explicitly states that the tool navigates in a sandboxed browser, does not submit forms or modify data, and that probing tests keyboard behavior. It also explains how different formats and parameters affect behavior, such as SARIF auto-filtering and exploration budgets.

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?

The description is front-loaded with the core purpose and key behavior. It includes a recommended usage and specific guidance for SPAs. It is moderately long but each sentence adds value. Minor redundancy could be trimmed, but overall it is well-structured.

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?

Given the tool has 33 parameters and no output schema, the description provides a good high-level context, including safety assurances, format recommendations, and SPA handling. It does not detail every parameter (the schema covers that), but it gives sufficient overall orientation for an AI agent.

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?

The input schema has 100% description coverage, so each parameter already has a meaning from the schema. The description does not add significant new semantics beyond the schema, but it does provide useful context for certain parameters like 'format' and 'waitForSelector'. According to the guidelines, baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: analyzing a web page for screen-reader navigation cost and returning scored findings. It also mentions specific behaviors like sandboxed navigation and read-only probing. However, it does not explicitly differentiate from sibling tools like 'analyze_pages', which may have similar functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides some usage guidance, such as recommending the 'sarif' format for concise output and advising 'waitForSelector' for SPAs. However, it does not specify when to use this tool versus alternatives like 'analyze_pages', 'trace_path', or others. It lacks explicit when-not and alternative statements.

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