Skip to main content
Glama
Sign In

SEO Score API

by io.github.SeoScoreAPI
OverviewDiscussionsAdmin

Competitive Keyword Audit

competitive_audit
Read-onlyIdempotent

Head-to-head SEO comparison of your page against a competitor's page with keyword-relevance scoring. Requires Pro plan ($39/mo) or higher.

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>",
      "competitor_url": "<competitor_url>",
      "keyword": "<keyword>"
    },
    "name": "competitive_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesYour page's full URL including the protocol, e.g. https://example.com/pricing.
keywordYesTarget keyword (max 200 characters).
competitor_urlYesThe competitor page's full URL including the protocol, e.g. https://competitor.com/pricing.

Output Schema

NameRequiredDescriptionDefault
youNoYour page's audit.
competitorNoThe competitor page's audit.

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 readOnlyHint=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so safety is covered structurally. The description adds genuinely new behavioral context by disclosing the plan entitlement required to invoke it, which the annotations do not convey. It omits cost/rate-limit details and scoring mechanics, so it is not 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.

Conciseness5/5

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

Two sentences, both front-loaded with the highest-value information: what the comparison is, then the hard prerequisite. No filler or restatement of the title.

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?

An output schema exists, so return values need no explanation, and the purpose plus plan requirement are stated. For an open-world, three-URL comparison tool it could still say more about URL validity expectations or what happens if a page is unreachable.

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% and all three parameters carry their own descriptions plus examples, so the schema does the heavy lifting. The description adds no meaning beyond it — it does not explain how url and competitor_url are compared or how keyword drives scoring.

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?

Names a specific verb and resource: 'Head-to-head SEO comparison of your page against a competitor's page with keyword-relevance scoring.' That is concrete enough to distinguish it from generic audit/crawl siblings, though it never explicitly contrasts itself with tools like compare or audit.

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?

Provides one real gating condition — 'Requires Pro plan ($39/mo) or higher' — which tells the agent when the call will fail. It gives no guidance on when to pick this over sibling tools such as compare or deep_audit, and no exclusions or preconditions about page URLs being live/crawlable.

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