Skip to main content
Glama
Sign In

SEO Score API

by io.github.SeoScoreAPI
OverviewDiscussionsAdmin

Batch SEO Audit

batch_audit
Read-onlyIdempotent

Audit multiple URLs in one call. Requires Starter plan ($5/mo) or higher. Returns one audit object per URL.

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

Input Schema

NameRequiredDescriptionDefault
urlsYesURLs to audit (1–10).
include_core_web_vitalsNoAlso measure Core Web Vitals for every URL. Slower: the batch can take a few minutes.

Output Schema

NameRequiredDescriptionDefault
resultsNoOne audit object per URL.

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 value the annotations cannot: a plan/pricing gate that causes auth-style failures, and the return shape of one audit object per URL. It does not say how partial failures among the 10 URLs are reported, which matters for a batch operation.

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 short sentences, front-loaded with the action, then the gate, then the result. No filler, no 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 not be explained in depth, and the simple two-parameter surface is well covered by the schema plus the plan requirement. The one real gap is batch failure semantics: whether one bad URL fails the whole call or yields partial results.

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%: the urls array already states the 1–10 range and include_core_web_vitals already documents the 'slower, few minutes' tradeoff. The description adds no parameter meaning beyond the schema, so the baseline 3 applies.

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 opens with a specific verb and resource ('Audit multiple URLs') and adds the batching scope ('in one call'), which is what separates it from the single-URL 'audit' sibling. It does not name that sibling outright, so the differentiation is implied by 'multiple' rather than stated.

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?

It gives a real prerequisite (Starter plan, $5/mo) which tells the agent when the call will fail, and the batch framing implies when to prefer it over a single audit. There is no explicit when-not guidance, no mention of limits beyond the schema's 1–10, and no named alternative to route to.

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