mcp-page-monitor

Overview Schema Source Related Servers Discussions Admin

monitor_page

Keep track of webpage changes by registering a URL for monitoring. Captures an initial snapshot immediately and can target a specific element via CSS selector.

Instructions

Register a URL to watch for changes. Takes an initial snapshot immediately. Optionally specify a CSS selector to monitor a specific element.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "monitor_page"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	The URL to monitor for changes
`label`	No	Human-readable label for this page
`selector`	No	CSS selector to monitor a specific element instead of the full page
`check_interval_minutes`	No	How often to check for changes (1 min to 7 days). Default: 60

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the immediate snapshot behavior, which is useful. However, it doesn't mention persistence, what happens on duplicate registrations, authorization requirements, or the return value. More behavioral disclosure would be expected for a write operation without annotations.

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

Conciseness5/5

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

The description is two sentences, front-loaded with the core action, and every word earns its place. No redundancy or fluff.

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?

The tool is simple with well-covered parameters, but there is no output schema and no mention of what the tool returns (likely an identifier used with siblings like check_changes). The workflow context is implied but not explicit. For a registration tool in a multi-step process, more guidance on integration would improve completeness.

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 schema already documents all parameters. The description's mention of 'optionally specify a CSS selector' adds no new information beyond what the schema states. It doesn't clarify formats, defaults, or parameter interactions, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Register a URL to watch for changes') and the resource (URL/page). It differentiates from siblings by focusing on registration/setup, whereas check_changes, analyze_change, list_monitored_pages, and remove_monitored_page handle other lifecycle stages.

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?

The context is clear: this tool registers a URL for change monitoring. It doesn't explicitly mention alternatives or when-not-to-use, but the description makes it the obvious starting point relative to siblings. There are no exclusions mentioned, which is fine for a registration tool.

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

Deploy Server