Skip to main content
Glama
Sign In

SEO Score API

by io.github.SeoScoreAPI
OverviewDiscussionsAdmin

GEO Audit (AI search visibility)

geo_audit
Read-onlyIdempotent

Run a GEO (Generative Engine Optimization) audit: 26 checks measuring how visible a page is to LLMs. Requires Basic plan ($15/mo) or higher; uses the plan's monthly GEO allowance.

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": "geo_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull page URL including the protocol, e.g. https://example.com/pricing.

Output Schema

NameRequiredDescriptionDefault
prioritiesNoPrioritized fixes, most important first. Each has the issue, a plain_english explanation and who_fixes_it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds valuable context the annotations cannot: this call is plan-gated and consumes the account's monthly GEO allowance, which is a real operational cost signal for an agent. It stops short of describing latency or output shape, but an output schema exists.

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?

Two tight sentences: the capability comes first, the cost/prerequisite constraint second. No filler, no repetition of the title, and the most decision-relevant constraints are front-loaded.

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?

For a single-parameter read-only audit with a schema-defined URL and an existing output schema, the description covers purpose, scope and the plan/allowance caveat. The only gap is that it doesn't tell the agent how this differs from the generic audit tools, which would matter for tool selection.

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?

There is a single parameter with 100% schema description coverage, including format, examples and maxLength, so the schema carries the semantics. The description adds nothing about the URL beyond what the schema already states, which is the expected baseline here.

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?

States a specific verb and resource ('Run a GEO audit') and defines the scope precisely: 26 checks measuring how visible a page is to LLMs. It does not explicitly contrast itself with related siblings like 'audit' or 'ai_readability', which keeps it from a 5.

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?

The description gives an eligibility condition (Basic plan or higher, consumes monthly GEO allowance) but no guidance on when to choose this over the plain 'audit' or 'ai_readability' tools. Usage is implied by the GEO/LLM-visibility framing rather than stated as a decision rule.

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

All SEO Score API 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