SEO Score API

Run AI Citation Tracker

run_citation_tracker

Run a citation tracker now. Every prompt x engine x sample counts as one check. A run needs all of its checks up front (the month's remaining allowance plus any top-up balance); if that is short the run is refused and nothing is spent. A check whose engine returned an error is not counted. A run that takes over 45 seconds returns {run_id, status: "running", poll} instead of the summary; it keeps running, so call get_citation_run with that run_id until status is completed.

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": {
      "tracker_id": "<tracker_id>"
    },
    "name": "run_citation_tracker"
  }
}

Input Schema

Name	Required	Description	Default
`tracker_id`	Yes	The tracker's id from list_citation_trackers or create_citation_tracker.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations only say the call is a non-idempotent, non-destructive open-world write; the description adds real operational context: allowance is reserved up front across monthly and top-up balance, an insufficient balance refuses the run with nothing spent, errored checks are not billed, and runs exceeding 45 seconds return a running status. That is far beyond what the structured fields convey.

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?

Five short sentences, front-loaded with the action and then ordered by decision relevance: cost, refusal, error accounting, timeout/polling. No filler and no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter mutation with an output schema and open-world semantics, the description covers the pieces an agent actually needs before calling: billing reservation, refusal outcome, run-duration behavior, and the exact recovery path. Nothing essential is missing.

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?

The single tracker_id parameter is fully described in the schema, including where to obtain it (list_citation_trackers / create_citation_tracker). The description adds the notion that the tracker's prompt/engine/sample configuration drives check count, which is useful, but adds no syntax or format detail beyond the schema.

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 citation tracker now') and clarifies the unit of work ('every prompt x engine x sample counts as one check'). It does not explicitly differentiate from nearby siblings such as citation_check or citation_auto_reload, so it stops short of 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?

Usage is implied by 'now' (immediate execution rather than scheduling) and there is a clear follow-up rule: call get_citation_run with the returned run_id until status is completed. However, there is no explicit when-not-to-use or comparison to the other citation-running siblings.

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.