Skip to main content
Glama
Sign In

AuditAE SEO MCP

by app.auditae
OverviewDiscussionsAdmin

Get a fix plan: exact edits that get the site cited by AI engines

get_fix_plan
Idempotent

Turn the site's audits into a ranked list of exact edits that get the brand cited by AI engines instead of competitors — sentences, FAQs, title and meta, JSON-LD, missing pages. Checks the live site first.

Billing: 50¢ per plan. Free (charged_cents=0): repeats within 24h, errors, and plans with nothing left to fix or only drafts/off-site work. dry_run: true quotes it free.

When to call: before editing a site for AI search, or when asked what to fix or why competitors get cited. page_url (recommended): one page, from the audit about it, else its Search Console queries; without it, site-wide.

already_done: true fixes are live (see evidence): skip. audit_stale (over 21 days) or site_changed_since_audit: say so, re-check first. draft: true fixes state facts the site doesn't show (needs_input): the user confirms or supplies each; never publish a draft as-is. Apply via how_to_apply, each fix's apply and code for platform (paired WordPress: the wp_* tools in tools); then submit_urls, inspect_url, and schedule_recheck with verify_prompts and audit_id.

Errors (unbilled; see message): site_not_found, audit_not_found, audit_brand_mismatch, no_audit, nothing_to_fix, not_diagnosed, no_relevant_audit, nothing_left_to_fix, truncated, empty_plan, fetch_failed (retry), not_configured, page_fetch_failed, page_not_on_domain, out_of_credits.

Returns { summary, platform, how_to_apply, fixes: [{priority, kind, page, title, why, already_done, evidence, draft?, needs_input?, find?, replace?, content?, faq?, meta?, code?, apply, tools, closes_prompts}], verify_prompts, site_check, audit_id, audit_stale, report_url, charged_cents, cache_hit }.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_fix_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoThe site's domain, e.g. "northwind.example". Needs a completed audit in this workspace, or Search Console connected for a page_url plan. Or pass site_id.
dry_runNotrue: return the price quote (estimated_cents, max_cents, breakdown) and what would run. Nothing runs or bills.
site_idNoA workspace site (list_sites) instead of domain.
audit_idNoPlan from this audit instead of the default (site-wide: the most comprehensive recent audit; with page_url: the one about that page).
page_urlNoA page on the site to plan exact edits for (full URL or path). Omit for a site-wide plan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / domain / description
      Previous value: -"The site's domain, e.g. \"northwind.example\". Needs a completed audit in this workspace, or Search Console connected for a page_url plan."New value: +"The site's domain, e.g. \"northwind.example\". Needs a completed audit in this workspace, or Search Console connected for a page_url plan. Or pass site_id."
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "true: return the price quote (estimated_cents, max_cents, breakdown) and what would run. Nothing runs or bills.",
+  "type": "boolean"
+}
    • changedInput schema / properties / page_url / description
      Previous value: -"A page on that domain to plan edits for (full URL or path). Omit for a site-wide plan."New value: +"A page on the site to plan exact edits for (full URL or path). Omit for a site-wide plan."
    • addedInput schema / properties / site_id
      Added value: +{
+  "description": "A workspace site (list_sites) instead of domain.",
+  "minLength": 1,
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "domain"
-]
  2. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"The site's domain, e.g. \"northwind.example\". Must have a completed audit in this workspace."New value: +"The site's domain, e.g. \"northwind.example\". Needs a completed audit in this workspace, or Search Console connected for a page_url plan."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The description adds substantial behavior beyond annotations: billing at 50¢, free cases including repeats/errors/nothing-to-fix, dry_run quoting, live-site checking, draft handling, and the apply/verify workflow. These details go well beyond the readOnly/openWorld/idempotent/non-destructive hints.

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

Conciseness5/5

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

The first sentence front-loads the core purpose, and later sections are organized around billing, usage, workflow, errors, and returns. Despite its density, every section supplies decision-relevant information and there is little filler.

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

Completeness5/5

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

For a complex, potentially billed plan-generation tool with no output schema, the description covers purpose, usage, billing, stale-audit handling, draft semantics, errors, and return shape. An agent has enough context to decide when and how to call it.

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 description coverage is already 100%, so the baseline is 3. The description adds meaningful guidance for page_url, including that it is recommended, that it scopes to one page, and that omission produces a site-wide plan.

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

Purpose4/5

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

The description gives a specific verb and resource: turning audits into a ranked list of exact edits, with concrete edit types (sentences, FAQs, title/meta, JSON-LD, missing pages). It is clear what the tool does, but it does not explicitly differentiate it from sibling tools such as get_audit or generate_schema.

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

Usage Guidelines5/5

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

It states when to call (before editing for AI search, or when asked what to fix or why competitors get cited) and gives practical routing between page_url and site-wide plans. It also includes when to skip already_done fixes and when to re-check stale audits first.

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 toolsInspect
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