Skip to main content
Glama

audit_seo_lite

Read-onlyIdempotent

FREE lite SEO technical audit of a single web page URL. Runs the same 13 checks as audit_seo but returns top-line results only: 0-100 score, A-F grade, search-visibility risk level, the page title, check counts, and the titles of the top gaps — per-check evidence and fixes are capped. Use this to triage whether a page needs the full audit_seo report, or call audit_seo directly for the complete evidence-backed scan.

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": {
      "url": "<url>"
    },
    "name": "audit_seo_lite"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesWeb page URL to audit, e.g. https://example.com/pricing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=true, so safety is covered. The description still adds real behavioral detail the annotations do not: it runs the same 13 checks as audit_seo, caps per-check evidence and fixes, and is free/lite in scope. It could go slightly further on how the 'capped' evidence limit actually manifests and whether the page must be publicly reachable (relevant given openWorldHint).

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?

Three sentences, front-loaded with the identity and output shape, then the return-value list, then the routing recommendation. No filler and no restatement of the name or annotations.

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 one-parameter, non-destructive read tool with no output schema, the description covers output contents, the relationship to the sibling, and the intended triage workflow. The only minor gap is that return values are only summarized, but that is acceptable since the exact field list is enumerated.

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?

With a single required parameter at 100% schema description coverage including an example URL, the schema fully carries parameter meaning. The description adds scope constraints ('single web page URL') but no format or edge-case guidance beyond that, which is appropriate for the 100%-coverage baseline.

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?

The description gives a specific verb and resource ('lite SEO technical audit of a single web page URL') and explicitly contrasts its output with the sibling's: top-line results only versus the full evidence-backed scan. It also enumerates what is returned (score, grade, risk level, title, check counts, gap titles), so an agent can distinguish it from audit_seo without opening either 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 both directions of the routing decision: use this 'to triage whether a page needs the full audit_seo report,' or 'call audit_seo directly for the complete evidence-backed scan.' That is an explicit when-to-use plus the named alternative, leaving nothing to inference.

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.