OnPage.dev

Rank fixes by traffic impact

prioritize_fixes

Read-onlyIdempotent

Use when Search Console, GA4, Ahrefs or Semrush data is available, also to explain a traffic drop (pass clicks_previous): ranks the fixes by the traffic or revenue they can win. Rank SEO fixes by how much traffic they can win, using data from the user's other connected tools. With GA4, also pass each page's organic conversions (key events) or revenue, and fixes are ranked by the money they can bring instead of clicks.

Input Schema

Name	Required	Description
`pages`	Yes
`detail`	No	brief = short summary.
`source`	No	Where the numbers come from.
`audit_id`	No	Optional id of a finished site audit, so pages are not scanned again.
`currency`	No	Currency of revenue, for example EUR or USD.
`memory_key`	No	site_memory key, records this call.

Output Schema

Name	Required	Description	Default
`mode`	No
`status`	Yes
`actions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 13, 2026

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."

Changed1 schema field changedOct 12, 2026

addedInput schema / properties / detail

Added value: +{
+  "description": "brief returns a short summary, default full.",
+  "enum": [
+    "full",
+    "brief"
+  ],
+  "type": "string"
+}

Changed1 schema field changedOct 12, 2026

addedInput schema / properties / memory_key

Added value: +{
+  "description": "Optional site_memory key, to record this call in the site memory.",
+  "maxLength": 80,
+  "type": "string"
+}

Changed3 schema fields changedOct 9, 2026
- addedInput schema / properties / audit_id / maxLength
```
Added value: +2000
```
- addedInput schema / properties / pages / items / properties / queries / items / properties / query / maxLength
```
Added value: +2000
```
- addedInput schema / properties / pages / items / properties / url / maxLength
```
Added value: +2048
```

Changed1 schema field changedOct 7, 2026

addedInput schema / properties / pages / items / properties / clicks_previous

Added value: +{
+  "description": "Clicks in an earlier period of the same length, for example the same 3 months a year or 6 months ago. Pages that lost clicks get a refresh fix.",
+  "minimum": 0,
+  "type": "number"
+}

Changed4 schema fields changedOct 7, 2026

addedInput schema / properties / currency

Added value: +{
+  "description": "Currency of revenue, for example EUR or USD.",
+  "maxLength": 3,
+  "type": "string"
+}

addedInput schema / properties / pages / items / properties / conversions

Added value: +{
+  "description": "Conversions (GA4 key events, sales, leads) from this page's organic visits in the same period.",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / pages / items / properties / revenue

Added value: +{
+  "description": "Revenue from this page's organic visits in the same period.",
+  "minimum": 0,
+  "type": "number"
+}

changedOutput schema / properties / mode / enum

Previous value: -[
-  "traffic",
-  "severity"
-]New value: +[
+  "revenue",
+  "conversions",
+  "traffic",
+  "severity"
+]

AddedOct 6, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety burden is light. The description adds real behavioral detail beyond them: passing clicks_previous triggers a refresh fix, and supplying GA4 conversions or revenue switches the ranking objective from clicks to money.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The usage condition and click-loss tip are front-loaded, but the second sentence largely restates the title and the first sentence's ranking claim without adding information, creating noticeable redundancy in a short description.

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?

With an output schema present, return values need not be described, and annotations cover safety. The description supplies the data-source preconditions and the two objective-switching behaviors an agent needs, leaving only minor gaps such as scope limits (max 10 pages).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 83%, so the baseline is 3. The description adds genuine semantics on top of the schema by explaining the purpose of clicks_previous (diagnosing traffic drops) and of conversions/revenue (re-ranking by monetary return), which the schema fields alone only hint at.

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: ranks SEO fixes by the traffic or revenue they can win. An agent can tell this is a prioritization tool rather than a raw data collector, though it never names the sibling it is distinguished from (e.g. find_opportunities or plan).

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?

Explicit trigger conditions are given: use when Search Console, GA4, Ahrefs or Semrush data is available, and additionally to explain a traffic drop by passing clicks_previous. It lacks exclusion criteria or named alternatives, but the when-to-use context is concrete.

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

All OnPage.dev tools Inspect

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.