Skip to main content
Glama
Sign In

SEO Score API

by io.github.SeoScoreAPI
OverviewDiscussionsAdmin

Add GEO Monitor

add_geo_monitor
Idempotent

Create a GEO monitor for a URL. Requires Basic plan or higher (the Basic plan runs weekly).

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

Input Schema

NameRequiredDescriptionDefault
urlYesFull page URL including the protocol, e.g. https://example.com/pricing.
frequencyNoHow often to re-run (Basic runs weekly).weekly
webhook_urlNoOptional https URL to POST alerts to.
alert_thresholdNoAlert when the score moves by this many points or more (negative = drop).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnly=false, destructive=false, idempotent=true), so the description is not carrying that burden. It adds the plan-tier requirement and the consequence that a Basic plan forces weekly frequency, which is real behavioral context, but it says nothing about auth expectations for webhook_url or what happens on duplicate creation beyond the idempotent hint.

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?

Two short sentences, front-loaded with the action and immediately followed by the access constraint. Nothing is redundant, though the parenthetical restates the plan note already present in the schema.

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 simple four-parameter creation tool with full schema coverage, annotations and an output schema, the description covers the one thing structured fields cannot: the plan-tier gate. Missing only sibling disambiguation and post-creation behavior, which are minor given the rich structured data.

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%, so the schema already documents url, frequency, webhook_url and alert_threshold. The description's plan note echoes what the frequency field's own schema text already says ('Basic runs weekly'), so it adds little meaning beyond the structured data.

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: 'Create a GEO monitor for a URL.' An agent can tell it is a creation tool scoped to GEO monitoring, but the description never distinguishes it from the sibling add_monitor, leaving the agent to infer the difference from names alone.

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 plan prerequisite ('Requires Basic plan or higher') is genuinely useful context for whether the call will succeed, but there is no explicit when-to-use guidance, no mention of what to do if a monitor already exists for the URL, and no contrast with add_monitor, geo_audit, or list_geo_monitors.

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