webaudit-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_pageA | One-shot audit of a URL: tracking tags, duplicate-tag risks, response-header hygiene, and resource counts, as a single readable report. Fast (no browser). For byte-level page weight use analyze_page_weight; for lab Core Web Vitals use measure_performance. |
| detect_tracking_tagsA | Static scan of a page's HTML for analytics/advertising tags: GA4, Google Tag Manager, Universal Analytics, Google Ads, Meta Pixel, TikTok, LinkedIn Insight, Hotjar, Microsoft Clarity, server-side/first-party tagging, and consent platforms. Reports IDs and where each was found. |
| find_duplicate_tagsA | Flag duplicate GA4/GTM/pixel installations and double-fire patterns: same ID initialized twice, multiple containers, hardcoded GA4 next to GTM, multiple pixel IDs, legacy UA leftovers. |
| measure_performanceA | Load the page in headless Chromium (Playwright) and capture lab metrics: TTFB, FCP, LCP, CLS, load times, request count and transfer sizes. Clearly labeled lab data, not field data. Requires the Playwright Chromium browser; returns the install command if missing. |
| analyze_page_weightA | Static page-weight analysis: counts and byte sizes of scripts, stylesheets, images, fonts and iframes referenced in the HTML, plus the largest third-party scripts. Measures up to 30 resources with capped, guarded requests. |
| check_headersA | Inspect the page's HTTP response headers: caching policy, compression, HSTS, CSP, clickjacking protection, referrer policy, CDN presence. Informational grades with explanations, no synthetic scores. |
| tracking_summaryA | Plain-language summary of a site's tracking setup written for a media buyer or marketer: what is installed, what it means for campaigns, consent posture, and issues to raise with the dev team. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Tools are mostly distinct with clear roles: audit_page is a composite overview while the others go deeper on specific aspects. The descriptions explicitly cross-reference each other, reducing ambiguity, though audit_page does overlap with several specialized tools.
Most names follow verb_noun convention (audit_page, detect_tracking_tags, find_duplicate_tags, measure_performance, analyze_page_weight, check_headers). tracking_summary breaks the pattern by being a noun phrase, causing a minor inconsistency.
Seven tools is well-scoped for a web audit server, covering tracking, performance, headers, and weight without redundancy or bloat. Each tool has a distinct purpose and contributes to the overall workflow.
The set covers the core audit lifecycle: detection, duplicate analysis, performance, page weight, headers, and a summary. Minor gaps exist (e.g., no field performance data or cookie inspection), but the provided tools handle the primary use cases effectively.