SEO Agent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEOAGENT_URL | No | The hosted endpoint, or a personal link https://mcp.seoagent.dev/u/le_…/mcp. Only needed for a self-hosted engine. | |
| SEOAGENT_API_KEY | No | A subscription key, for environments where a config file is inconvenient (CI, containers). |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_sitesA | Search the free list of 25 backlink sites by name, domain, method, DA and dofollow. auto_build marks the ones build_link can do by itself. The result also lists locked higher-DA matches from the full library; when the user wants those, offer the subscription (see ask_the_user). Methods: profile_website_field, article_post, bookmark_submit, url_shortener, page_builder, forum_post, directory_listing, document_share, social_post, comment, qa_answer, forum_signature. |
| get_methodC | The method for one site: playbook for its link type, what it requires, the ordered actions with exact button names, and which action places the link. |
| build_linkA | Build one backlink in a browser on this machine (login-free sites: shorteners and open submit forms), with a proof screenshot. On other sites it returns the method for you to follow. Status placed means verified live; gated means a captcha appeared: ask the user, then retry with headless=false or skip. |
| verify_linkA | Fetch a live page and confirm the backlink: target URL present as a hyperlink, anchor text, and whether it is nofollow. |
| log_linkC | Record a link you placed by following a method: status placed (verified live), unverified, manual or failed. |
| list_resultsC | Every link built or logged on this machine. |
| accountA | Current plan, links placed, and how to upgrade. Call it when the user asks about credits, pricing or limits. |
| upgradeB | The subscription: every one of 1,245 sites and the whole engine, yearly or monthly. Returns the payment links and what to do after paying. |
| activateA | Activate a subscription key (le_...) or a personal MCP link from the purchase success page. Verifies it with the hosted engine and saves it here; from then on every hosted tool is available. |
| library_summaryB | What the free list contains and what a subscription adds. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| build_backlink | Build one backlink on a free-list site by following its method, then verify it. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools have clear boundaries: search sites, get method, build, verify, log, and list results are distinct steps. The main confusion risk is build_link returning a method instead of only building, which overlaps somewhat with get_method, and search_sites vs library_summary both touch link discovery.
The core workflow tools follow a verb_noun pattern: search_sites, get_method, build_link, verify_link, log_link, list_results. However, account, upgrade, activate, and library_summary break the pattern with bare nouns or verbs, making the naming convention mixed but still readable.
Ten tools is well within the ideal range and each supports a clear part of the SEO backlink workflow. The inclusion of account, upgrade, activate, and library_summary may feel sales-oriented, but they are relevant to the server's subscription-gated functionality.
The core lifecycle is covered: discover sites, inspect the method, build or manually place links, verify them, log the result, and list all records. Minor gaps exist such as no way to update or delete a logged link and no direct browse of the full paid library, but agents can work around these.