SEO Score API

Add Score Monitor

add_monitor

Add a URL to score monitoring: it is re-audited on a schedule (daily or weekly) and the account owner is emailed when the score drops. Each plan allows a set number of monitors; the error says when the limit is reached.

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_monitor"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Full page URL including the protocol, e.g. https://example.com/pricing.
`frequency`	No	How often to re-audit.	daily

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Goes meaningfully beyond the annotations: it discloses the recurring side effect (re-audit on a schedule), the outbound notification (account owner emailed on score drop), and the quota failure mode (plan monitor limit surfaces as an error). Annotations cover safety and idempotency but not these operational consequences, and the description fills that gap. It does not say what happens if the same URL is added twice, which the idempotentHint=false makes relevant.

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 compact sentences, front-loaded with the action, and each clause carries real information (schedule, notification, quota). The '(daily or weekly)' parenthetical duplicates the schema enum and the quota sentence is slightly tangential, keeping it out of top marks.

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 two-parameter mutation tool with an output schema and full annotation coverage, the definition supplies what the structured fields do not: the recurring behavior, the notification, and the quota error. Only the duplicate-URL case and how to inspect existing monitors are left unaddressed.

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 coverage is 100% and both parameters are fully documented in the schema, so baseline is 3. The description only restates the frequency enum ('daily or weekly') and adds no format or constraint detail beyond the schema's own URL guidance.

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?

Specific verb plus resource: 'Add a URL to score monitoring', extended with what monitoring actually does (scheduled re-audit, email on score drop). It is distinct from add_geo_monitor by naming 'score' monitoring, though the contrast to the geo variant is only implicit.

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 conveys the context in which monitoring applies (ongoing scheduled re-checks rather than a one-off audit), which implies its role versus audit-style siblings. It never explicitly says when to choose this over add_geo_monitor or a one-time audit, and gives no prerequisites beyond the plan limit.

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 tools Inspect

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.