OnPage.dev

Technical SEO

technical

Read-onlyIdempotent

Technical checks across pages and logs. Pick with mode: hreflang = Hreflang across language versions, with the corrected tag set. Needs url. parameters = URL parameters and filters that waste crawl budget. duplicates = Duplicate and near-duplicate pages. Needs audit_id. extract = One value pulled from many pages. Needs urls. logs = Access logs: what Googlebot and AI crawlers really crawl, with IP verification. Needs log.

Input Schema

Name	Required	Description
`log`	No	Raw access log lines, one request per line.
`url`	No	Full address of one language version of the page.
`mode`	No	Default hreflang.
`urls`	No	Optional extra URLs, for example from server logs or Search Console.
`regex`	No	A regular expression; the first group is returned if there is one, otherwise the whole match.
`detail`	No	brief = short summary.
`jsonld`	No	A JSON-LD path: the @type, then the properties, for example Product.offers.price or Article.author.name.
`audit_id`	No	Id of a completed site audit.
`selector`	No	CSS selector, for example .price, h1 or link[rel=canonical].
`attribute`	No	With selector: read this attribute instead of the text, for example href or content.
`memory_key`	No	site_memory key, records this call.
`sitemap_urls`	No	Optional: the URLs from the site's sitemap, to find pages bots never crawl.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

removedOutput schema / description

Removed value: -"The result as structured data; fields depend on mode."

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

AddedOct 12, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds mode-specific behavior ('IP verification', 'corrected tag set', 'waste crawl budget'), which is useful, but says nothing about rate limits, cost, or how results differ per mode.

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?

The definition is densely front-loaded: the general purpose opens, then each mode is a compact clause. The mode list reads as a run-on, but no sentence is wasted.

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 12 params but 0 required, the mode-to-parameter dependency is the critical missing piece from the schema, and the description supplies it. An output schema exists, so return values need not be explained, and the remaining gap is only the absence of sibling routing.

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 100%, so the schema documents every parameter and the baseline is 3. The description adds real value beyond that by mapping which parameter each mode requires, which the schema cannot express on its own.

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?

The description enumerates all five modes (hreflang, parameters, duplicates, extract, logs) and says what each finds, so an agent understands the tool's scope. The umbrella phrase 'Technical checks across pages and logs' is generic, and no sibling tool is named for contrast, which keeps it 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 Guidelines4/5

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

'Pick with mode' plus per-mode requirements ('Needs url', 'Needs audit_id', 'Needs urls', 'Needs log') tells the agent exactly how to invoke each branch. There is no explicit when-not-to-use and no routing to siblings like sitemap or scan_page, so it stops short of a 5.

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.