Skip to main content
Glama

OnPage.dev

by dev.onpage
OverviewDiscussionsAdmin

Smart rank tracker that knows what matters

track_rankings

Use for ongoing rank tracking without picking keywords by hand. Each run, fetch Search Console rows by query and page (last 7 or 28 days) and, if connected, the rows of Ahrefs Rank Tracker (rank-tracker-overview) or Semrush Position Tracking, plus GA4 conversions or revenue per landing page if available, and pass them with the tracker_id (leave it out on the first run to create a tracker).

Input Schema

NameRequiredDescriptionDefault
siteNoYour site. Needed on the first run.
actionNorun (default), status or stop.
detailNobrief = short summary.
gsc_rowsNoSearch Console rows by query and page for the period.
fix_log_idNoOptional fix log (log_fix) whose pages count as work done.
memory_keyNosite_memory key, records this call.
tracker_idNoFrom the first run. Leave out to create a tracker.
conversionsNoOptional GA4 key events or revenue per landing page.
webhook_urlNoOptional https webhook for the changes (Slack and Discord work).
tracker_rowsNoAhrefs Rank Tracker or Semrush Position Tracking rows.
money_keywordsNoOptional keywords you always want followed.

Output Schema

NameRequiredDescriptionDefault
runsNo
eventsNo
groupsNo
trackerIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / detail / description
      Previous value: -"brief returns a short summary, default full."New value: +"brief = short summary."
    • changedInput schema / properties / memory_key / description
      Previous value: -"Optional site_memory key, to record this call in the site memory."New value: +"site_memory key, records this call."
  2. Changed1 schema field changed
    • addedInput schema / properties / detail
      Added value: +{
+  "description": "brief returns a short summary, default full.",
+  "enum": [
+    "full",
+    "brief"
+  ],
+  "type": "string"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / memory_key
      Added value: +{
+  "description": "Optional site_memory key, to record this call in the site memory.",
+  "maxLength": 80,
+  "type": "string"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / fix_log_id / description
      Previous value: -"Optional fix log (log_fix) whose pages count as work done. Kept on the tracker."New value: +"Optional fix log (log_fix) whose pages count as work done."
  5. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, idempotentHint=false, openWorldHint=true, so the mutation/open-world nature is already flagged. The description adds real value beyond that: it discloses the stateful create-on-first-run behavior (omit tracker_id to create a tracker) and the per-run data-collection workflow.

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?

Front-loaded with the primary use case and packed into a single dense sentence with no filler. It is a bit run-on and reads like an instruction sequence, but every clause carries operational content.

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

Completeness3/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 described, and the 'run' path is well covered. However the tool exposes action=run/status/stop, detail, memory_key, fix_log_id, webhook_url and money_keywords, and the description explains none of the status/stop or notification behavior — a notable gap for an 11-parameter tool.

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 baseline is 3. Most of what the description says about parameters (tracker_id from first run, rows sourced from GSC/Ahrefs/Semrush/GA4) is already echoed in the schema descriptions. It does add the 'last 7 or 28 days' period hint, but that is marginal.

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+resource (ongoing rank tracking) and describes the concrete data sources it aggregates (Search Console, Ahrefs Rank Tracker, Semrush Position Tracking, GA4). An agent can tell it is a rank-tracking aggregation tool, though it never explicitly names or differentiates from the sibling 'tracking'/'watch' tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use for ongoing rank tracking without picking keywords by hand' gives a clear use context, and it explains the first-run bootstrap ('leave it out on the first run to create a tracker'). It stops short of stating when NOT to use it or which sibling to prefer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All OnPage.dev toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources