Agent SEO Engine
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
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
Each tool targets a distinct SEO function (e.g., image alt, intent detection, privacy audit), with no apparent overlap in purpose.
While all tools share the 'agent_seo_' prefix, some follow a verb_noun pattern (check_image_alt, detect_intent, prioritize_opportunity, score_content) while others are plain nouns (connection_status, manifest, privacy_audit), creating inconsistency.
Seven tools is a reasonable number for a specialized SEO assistant, providing focused functionality without being overly numerous or sparse.
The set covers important SEO checks (alt text, content score, privacy) but lacks common tasks like keyword research, meta tag optimization, or sitemap management, indicating notable gaps.