Skip to main content
Glama

SEO Site Audit MCP: On-Page Checks and Page Speed

SEO site audit for pages

run_seo_site_audit
Read-onlyIdempotent

SEO site audit: on-page and technical SEO checks for up to 5 pages, with status code, on-page score, title, meta description, H1, canonical, word count, links, load time and every failed check. Costs API credits per page.

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": {
      "urls": "<urls>"
    },
    "name": "run_seo_site_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesUp to 5 page URLs to audit.
javascriptNoRender JavaScript before auditing (slower, costs more). Default false.

Output Schema

NameRequiredDescriptionDefault
resultYes
billingYes
dashboardUrlNoDashboard page where this tool also runs in the app; its call history and costs are linked from there. Share it when the user asks what they ran or spent.
creditsNoticeNoLow API credit balance: tell the user once, with this link to add credits. Never open it automatically.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / creditsNotice
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Low API credit balance: tell the user once, with this link to add credits. Never open it automatically.",
      +  "properties": {
      +    "label": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "label",
      +    "url"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • removedOutput schema / properties / creditsNotice
      Removed value: -{
      -  "additionalProperties": false,
      -  "description": "Low API credit balance: tell the user once, with this link to add credits. Never open it automatically.",
      -  "properties": {
      -    "label": {
      -      "type": "string"
      -    },
      -    "url": {
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "label",
      -    "url"
      -  ],
      -  "type": "object"
      -}
  3. Changed1 schema field changed
    • addedOutput schema / properties / creditsNotice
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Low API credit balance: tell the user once, with this link to add credits. Never open it automatically.",
      +  "properties": {
      +    "label": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "label",
      +    "url"
      +  ],
      +  "type": "object"
      +}
  4. Changed1 schema field changed
    • changedOutput schema / properties / dashboardUrl / description
      Previous value: -"Dashboard page with this server's call history and costs. Share it when the user asks what they ran or spent."New value: +"Dashboard page where this tool also runs in the app; its call history and costs are linked from there. Share it when the user asks what they ran or spent."
  5. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive behavior, so the description's main added value is the commercial constraint: 'Costs API credits per page', which tells an agent to avoid wasteful bulk calls. It also discloses the 5-page ceiling and that every failed check is returned, but says nothing about rate limits or error behavior on unreachable URLs.

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?

A single front-loaded sentence that opens with the verb-resource and finishes with the cost caveat. The long field enumeration is informative but could be trimmed since an output schema exists.

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 an output schema, full annotation coverage, and fully documented parameters, the description only needs to add scope and cost, which it does. Missing only light guidance on alternatives and failure handling for invalid URLs.

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

Parameters3/5

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

Schema description coverage is 100%, including the 5-item max, URI format, and the 'javascript' flag with its performance/cost tradeoff, so the schema does the heavy lifting. The description only echoes the page cap and adds no format or default detail, which is the baseline 3 given full schema coverage.

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 and resource ('SEO site audit: on-page and technical SEO checks') and scopes it to 'up to 5 pages', which separates it from single-purpose siblings like check_if_url_is_indexed or get_page_speed_scores. The enumerated result fields (status code, on-page score, title, meta, H1, canonical, word count, links, load time, failed checks) make the deliverable unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied: the 5-page cap suggests this is for small batches, and the credit-cost note hints at when to be selective. There is no explicit statement of when to choose this over inspect_url_in_google, get_page_speed_scores, or the per-URL checks, and no exclusions (e.g. internal/private URLs).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources