web-presence-audit
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_form_platformA | Detect which form/website platform a site runs (WPForms, Contact Form 7, Wix, Squarespace, Jotform, Gravity Forms, HubSpot, Typeform, Drupal, or 'unknown'). The platform PREDICTS whether automated form outreach can work: WordPress/WPForms and CF7 accept standard fill-and-submit; Wix forms fire no network traffic on automated submits (verified in live campaigns) — use email or social there instead. Returns the platform, a plain-English outreach note, and the count of visible form fields (hidden honeypot fields excluded). Args: url: The page to check, e.g. "https://example.co.uk" or "https://example.co.uk/contact". |
| check_tap_to_callA | Check whether the phone number on a page is a clickable tel: link (tap-to-call). On mobile, a plain-text number cannot be tapped — visitors must retype it, and most won't. Returns every tel: link found, any plain-text UK numbers, and a verdict ('ok', 'leak', or 'no_phone_found'). Args: url: The page to check, e.g. "https://example.co.uk". |
| check_nap_consistencyA | Check the phone number (NAP: Name/Address/Phone consistency) between the business's own website and the free UK directories (thomsonlocal, TrustATrader), via Bing's public RSS search. A mismatched number confuses both Google and dialling customers. Returns the phone found on each source and a verdict: 'consistent', 'inconsistent', or 'insufficient data'. Args: business: Business name, e.g. "Driver Plumbing & Heating". city: UK city, e.g. "Leicester". trade: Trade keyword (plumber, electrician...) — guessed from the business name if omitted. website_url: The business's website if you know it — skips the search step and makes the NAP comparison stronger. |
| audit_websiteB | Run the quick website hygiene checks: reachable?, HTTPS?, mobile viewport tag?, page weight, load time, title and meta description. Each missing item is a concrete fixable finding for an audit report. Args: url: The website to check, e.g. "https://example.co.uk". |
| find_websiteA | Find a business's own website via Bing's public RSS search. Only a result that genuinely matches the business name (with a distinguishing word — not just trade words) and is not a directory or social site is returned. Returns the URL, or an honest 'not found' with the search URL so a human can double-check. Args: business: Business name, e.g. "Driver Plumbing & Heating". city: UK city, e.g. "Leicester". |
| run_full_auditA | Run the COMPLETE lead-leak audit on a UK local service business: search presence, website hygiene, form platform, tap-to-call, NAP consistency across free directories, and the 3BestRated top-3 competitors. Returns every finding plus a prioritized leak list. This is the full methodology used in real paid audits. Runs 6-10 free web requests; expect about 10-30 seconds. Args: business: Business name, e.g. "Driver Plumbing & Heating". city: UK city, e.g. "Leicester". trade: Trade keyword — guessed from the name if omitted. website_url: Known website URL — skips discovery if provided. |
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 6 tools
Each tool targets a distinct check: form platform, tap-to-call, NAP consistency, website hygiene, and website discovery are all clearly separated by purpose. The only overlap is run_full_audit, which intentionally composes the others; its description clearly frames it as the complete composite, so an agent can still choose correctly.
All names are snake_case following a verb_noun pattern (check_form_platform, audit_website, find_website, run_full_audit). The verbs vary (check/audit/find/run) but the structural convention is consistent and readable.
Six tools is well-scoped for a focused web-presence audit: five atomic checks plus one composite orchestrator. Each tool earns its place with no redundancy or padding.
The surface covers website discovery, hygiene, form platform, tap-to-call, and NAP consistency, plus a full audit — solid lifecycle coverage for the domain. Minor gap: competitor/review checks are only reachable through run_full_audit rather than a standalone tool, but agents can still access them.