Skip to main content
Glama

analyze_url

Analyze a web page to measure screen-reader navigation cost, returning scored findings on how easily assistive-technology users can discover 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
focusNoOnly analyze targets within these landmarks.
probeNoRun keyboard probes on interactive targets. Adds ~30-60s.
deviceNoPlaywright device name for emulation (e.g., 'iPhone 14')
formatNoOutput format. 'sarif' (recommended) filters to actionable findings only.sarif
channelNoBrowser channel: chrome, chrome-beta, msedge. Bypasses shared pool.
excludeNoGlob patterns to exclude targets by name/role/kind.
exploreNoExplore hidden branches (menus, tabs, dialogs). Use with format='sarif' to avoid output overflow.
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
stealthNoApply anti-bot-detection defaults. Pair with channel for Cloudflare-protected sites.
timeoutNoPage load timeout in ms
waitTimeNoAdditional ms to wait after page load.
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
autoScrollNoScroll to the bottom of the page in steps before capture so IntersectionObserver-driven lazy content materializes. Capped at 20 scrolls / 30 s; emits an auto-scrolled info diagnostic.
goalTargetNoExact-ish target id, name, role, kind, or selector hint for goal-directed probing.
probeHoverNoHover candidate triggers to surface hover-only popups/tooltips without attribute hints. Diffs ariaSnapshot before/after each hover; new content becomes _hoverContent enrichment. Default budget 10 candidates; adds ~7-8 s.
allowActionNoGlob patterns for controls that should be explorable despite the safety policy.
goalPatternNoGlob pattern matched against target id/name/role/kind/selector for goal-directed probing.
maxFindingsNoMaximum detailed findings to return.
minSeverityNoOnly include findings at this severity or worse. Reduces output size.
probeBudgetNoMaximum number of targets for the generic probe. Overrides probeMode's generic budget.
summaryOnlyNoReturn compact summary stats. Use for quick page health checks.
detectRoutesNoRecord SPA route changes (history.pushState/replaceState, popstate, hashchange) that fire during analysis. Surfaces an spa-route-changes info diagnostic when any are observed.
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.
storageStateNoPath to Playwright storageState JSON (cookies + localStorage). Must be within cwd.
walkTabOrderNoPress Tab up to 30 times and record the focused-element sequence so the analyzer can flag positive-tabindex anti-patterns and focus traps. Adds ~1-3 s.
descendFramesNoDescend into child iframes during capture (capped at 20 frames). Appends frame targets with frame-URL attribution; Chromium can recover many inaccessible cross-origin OOPIF trees via CDP. Surfaces a frames-descended info diagnostic when any frame content is captured.
diffViewportsNoCapture the URL at desktop (1280×800) and mobile (375×667) viewports and diff the resulting target / landmark / heading lists. Surfaces a viewport-divergence diagnostic when content is set to display:none on small screens. Adds ~3-5 s.
entrySelectorNoActivate this trigger before capture/probe, then prioritize newly revealed targets.
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.
includeStatesNoInclude captured states in JSON output for passing to trace_path's statesJson parameter. Uses compact format (~5KB).
probeSelectorNoCSS selectors that narrow probes without changing capture/scoring.
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.
scopeSelectorNoCSS selectors that define the subtree(s) to capture, score, and probe.
dismissBannersNoBest-effort dismiss of cookie/consent/GDPR banners. Clicks safe-accept buttons (Accept / OK / Got it / Allow all); explicitly skips Decline/Manage/Customize. Emits a banners-dismissed info diagnostic.
exploreTimeoutNoTotal exploration timeout in ms; includes initial/revealed probe time when probe is enabled (default: 60000).
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).
excludeSelectorNoCSS selectors to hide from analysis (set aria-hidden before capture).
waitForSelectorNoCSS selector to wait for before capturing (essential for SPAs).
exploreMaxTargetsNoMax accumulated targets before exploration stops early (default: 2000).
Behavior5/5

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

With no annotations provided, the description fully discloses that the tool navigates in a sandboxed browser, probes keyboards, does not submit forms, and explains output sizes, exploration budgets, and timeouts in detail.

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 well-structured with bolded recommendations and clear sections. Every sentence adds useful information, and it efficiently covers the tool's purpose, key parameters, and usage tips without redundancy.

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?

Despite 40 parameters and no output schema, the description thoroughly explains return formats, behavioral aspects like exploration and probing, and practical considerations such as SPA handling, anti-bot measures, and output size. It is complete for effective tool use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant value beyond the schema: it recommends default profiles, explains the impact of exploreDepth and exploreBudget on latency, and clarifies the necessity of waitForSelector for SPAs.

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 states the tool analyzes a web page for screen-reader navigation cost and returns scored findings. It clearly distinguishes from siblings like analyze_pages and validate_url by specifying the focus on accessibility testing.

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 recommends using SARIF format for concise output, warns about SPAs needing waitForSelector, and mentions that probes test keyboard behavior without modifying data. While it doesn't explicitly exclude use cases, it provides sufficient context for appropriate use.

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