OnPage.dev

Keep watching

watch

Monitoring that runs on its own and posts changes to a webhook. Each kind takes action create (default), status or stop where it applies. Pick with mode: page = Watch one page (or a competitor page with competitor_of) for SEO changes. Needs url. page_status = Latest result of a page watch. Needs watch_id. page_stop = Stop a page watch. Needs watch_id. site_audit = Audit the whole site every 1, 7 or 30 days and alert on regressions. guard = Every 6 hours: robots.txt, sitemap, https, noindex and canonical on key pages, for deploy accidents. competitors = Weekly new, updated and removed pages from competitors' sitemaps, flagged by your topics.

Input Schema

Name	Required	Description
`url`	No	Full address, for example https://example.com/pricing.
`mode`	No	Default page.
`pages`	No	Key pages to guard besides the home page (money pages first).
`action`	No	create (default), status or stop.
`detail`	No	brief = short summary.
`topics`	No	Your topics or keywords, to flag overlapping pages.
`guard_id`	No	For status and stop.
`watch_id`	No	For status and stop.
`max_pages`	No	Pages per audit, default 25.
`every_days`	No	How often, default 7.
`memory_key`	No	site_memory key, records this call.
`competitors`	No	Competitor home pages.
`schedule_id`	No	For status and stop.
`webhook_url`	No	Optional https URL that receives a JSON POST when something changes, for example a Slack or Discord incoming webhook.
`competitor_of`	No	Optional: your own page.

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

AddedOct 12, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Beyond annotations (readOnlyHint=false, openWorldHint=true), the description discloses that the tool runs automatically, posts to a webhook, and follows schedules (every 1/7/30 days, every 6 hours, weekly). It also describes mode-specific actions and required IDs, which enriches behavioral understanding.

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 description is front-loaded with the core purpose and then organises mode details in a readable sequence. While dense, it avoids filler and is appropriately sized for a 15-parameter multi-mode tool.

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 and full schema descriptions, the description need not explain return values. It covers the main modes and schedules, but leaves action/ID usage for guard, site_audit, and competitors unspecified, which is a minor gap.

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 baseline is 3. The description adds cross-parameter meaning by mapping modes to required parameters (e.g., page needs url, page_status needs watch_id), though it omits such mapping for guard, site_audit, and competitors.

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 states the tool's purpose as autonomous monitoring that posts changes to a webhook, and enumerates six modes with specific resources (page, site, robots.txt, etc.). It does not contrast the tool with siblings like site_audit or tracking, so it stops short of the top score.

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?

It gives clear context for each mode (e.g., page for SEO changes, guard for deploy accidents) and notes action create/status/stop. However, it offers no explicit guidance on when to choose this tool over alternatives such as the site_audit or tracking siblings.

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.