AuditAE SEO MCP

Add a site to this agent workspace

add_site

Idempotent

Create (or update) a site in the agent workspace and return its site_id, for the tools that take one (explore_llm_mentions, explore_web_mentions, mine_competitor_prompts, find_content_gap, crawl_site, detect_tech_stack, get_backlink_summary, submit_urls, schedule_recheck). Creates the workspace on first use and returns its API key.

Billing: bundled — free.

Example: { domain: "linear.app", brand: "Linear", competitor_domains: ["asana.com"] }

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>",
      "brand": "<brand>"
    },
    "name": "add_site"
  }
}

Input Schema

Name	Required	Description
`brand`	Yes	Brand name as written in prose.
`domain`	Yes
`competitor_domains`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare idempotentHint=true, destructiveHint=false, and openWorldHint=true. The description adds value beyond these: workspace auto-creation on first use, the API key return, and billing ('bundled — free'). It does not detail failure modes or what 'update' overwrites, keeping it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the primary purpose before the dependent-tool list, billing, and example. The nine-tool enumeration is long but functional; overall it reads tightly with no redundant filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly supplies the return values (site_id, API key), plus billing and a worked example. An agent has enough to invoke it, though a note on duplicate handling / relationship to list_sites would make it fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33% (only 'brand' documented), so the description must compensate. The concrete example { domain: 'linear.app', brand: 'Linear', competitor_domains: ['asana.com'] } demonstrates the format for all three params, materially clarifying domain and competitor_domains beyond the schema. It does not explain the semantic role of competitor_domains, so not a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Create (or update) a site in the agent workspace') and its return value ('site_id'). It further distinguishes itself by naming exactly which sibling tools consume that site_id, so an agent can place it in a workflow without inspecting other schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context: this is the prerequisite whose site_id feeds nine named downstream tools, and it 'Creates the workspace on first use.' It stops short of explicit when-not guidance (e.g., 'use list_sites first to avoid duplicates'), but the 'create or update' framing implies idempotent, safe-to-call-anytime behavior.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AuditAE SEO MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?