untapped-plugins
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| page_factsB | Free. Fetch one page and report what search engines read: status, redirect chain, title, meta description, robots (meta + header + robots.txt for Googlebot), canonical, H1/H2s, schema types, hreflang, word count, links, images without alt, and problems found. |
| audit_pagesB | Free. page_facts for every URL in a sitemap (default /sitemap.xml) or a list, plus problems across pages: duplicate titles/H1s/meta, noindex or non-200 pages listed in the sitemap, canonicals pointing elsewhere, missing titles/H1s/meta. |
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 2 tools
page_facts handles a single URL's SEO facts while audit_pages extends that to sitemaps or lists with cross-page problems. The single-vs-bulk boundary is clear, though audit_pages operationally subsumes page_facts for lists, creating mild overlap.
Both names use snake_case and are readable, but they follow different grammatical patterns (noun phrase 'page_facts' vs verb-object 'audit_pages'), so there is no single predictable convention.
Two tools is minimal for an SEO auditing server; each tool is broad and earns its place, but the surface feels thin and likely leaves users wanting more granular operations.
The pair covers single-page facts and bulk sitemap/list auditing, including aggregate problems—core SEO audit workflows. Minor gaps remain around historical comparisons or more granular inspection of individual resources like raw headers.