OnPage.dev

Recrawl

request_recrawl

Idempotent

Get changed pages recrawled. Pick with mode: recrawl = Check pages are indexable, sitemap lastmod entries, IndexNow and Search Console steps (default). Needs urls. indexnow = Submit URLs to IndexNow, or set up the key. Needs urls.

Input Schema

Name	Required	Description
`key`	No	The site's IndexNow key (8 to 128 letters, digits or dashes).
`mode`	No	Default recrawl.
`urls`	No	Changed pages on one site.
`detail`	No	brief = short summary.
`memory_key`	No	site_memory key, records this call.
`indexnow_key`	No	Optional IndexNow key that is live at /<key>.txt.

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

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

Changed9 schema fields changedOct 12, 2026

changedInput schema / properties / indexnow_key / description

Previous value: -"Optional IndexNow key that is live at /<key>.txt. Without it, submit_indexnow explains the setup."New value: +"Optional IndexNow key that is live at /<key>.txt."

addedInput schema / properties / key

Added value: +{
+  "description": "The site's IndexNow key (8 to 128 letters, digits or dashes).",
+  "maxLength": 2000,
+  "type": "string"
+}

addedInput schema / properties / mode

Added value: +{
+  "description": "Default recrawl.",
+  "enum": [
+    "recrawl",
+    "indexnow"
+  ],
+  "type": "string"
+}

removedInput schema / properties / urls / maxItems
```
Removed value: -10
```
removedInput schema / properties / urls / minItems
```
Removed value: -1
```
removedInput schema / required
```
Removed value: -[
-  "urls"
-]
```

addedOutput schema / description

Added value: +"The result as structured data; fields depend on mode."

removedOutput schema / properties

Removed value: -{
-  "indexNow": {
-    "type": [
-      "object",
-      "null"
-    ]
-  },
-  "pages": {
-    "items": {
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "sitemap": {
-    "type": "string"
-  }
-}

removedOutput schema / required
```
Removed value: -[
-  "pages"
-]
```

AddedOct 12, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false and openWorld=true, so the safety profile is covered. The description adds meaningful behavioral detail beyond that: it enumerates the steps the recrawl performs (indexability check, sitemap lastmod, IndexNow, Search Console) and discloses a practical requirement ('Needs urls') that the schema does not enforce, since zero parameters are marked required.

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 core action is front-loaded in the first sentence, then mode semantics follow in a compact form. 'Needs urls' is repeated for each mode, which is mildly redundant but serves as an emphasis of the shared requirement.

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?

An output schema exists, so return values need not be explained. For a 6-parameter, 0-required tool the description supplies the missing mode semantics and the practical 'needs urls' constraint, leaving little an agent needs but doesn't have.

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 description coverage is 100%, so the baseline is 3. The description earns a bump because the schema's own enum descriptions are terse ('Default recrawl'), whereas the description explains what 'recrawl' and 'indexnow' actually do and flags that 'urls' is effectively needed for both, adding meaning the schema lacks.

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 ('Get changed pages recrawled') and then breaks the tool into its two operating modes, so the agent understands what it does. It doesn't name or contrast against sibling tools like sitemap or a dedicated IndexNow tool, so sibling differentiation 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 Guidelines4/5

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

Explicitly tells the agent how to choose a mode: 'recrawl' (default) versus 'indexnow', and describes what each does. This is clear when-to-use guidance for the sub-behaviors, though it gives no when-not-to-use or cross-tool alternative.

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.