Skip to main content
Glama
Sign In
MCP Browser

MCP Browser

by wgarrido
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

monitor_page

Monitors a web page for content changes and retrieves updates. Use start, check, stop, and list actions to manage active monitors for any URL or CSS selector.

Instructions

Monitor a web page for content changes. Use 'start' to begin monitoring, 'check' to retrieve changes, 'stop' to end monitoring, or 'list' to see all active monitors.

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": {
      "action": "<action>"
    },
    "name": "monitor_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoURL to monitor (required for 'start')
actionYesAction to perform
selectorNoCSS selector to monitor for changes (default: 'body')
monitor_idNoMonitor ID (required for 'check' and 'stop')
interval_secondsNoPolling interval in seconds (default: 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that monitors exist and can be listed or stopped, but it does not state whether start launches a background process, whether checks consume or destroy state, whether resources persist, or what side effects monitoring has. A stateful tool needs more explicit lifecycle behavior.

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?

Two sentences with no filler, front-loaded with the core purpose. The second sentence compactly maps all four actions without unnecessary elaboration.

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 action surface is covered clearly, but the broader behavior is underspecified: there is no output schema, no indication of what 'start' returns, no clarification of whether monitoring is server-side or tied to an open tab, and no cleanup or rate-limit guidance. For a stateful tool with no annotations, this leaves important gaps an agent would have to infer.

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 coverage is 100%, so the schema already documents every parameter, giving a baseline of 3. The description adds some action-to-parameter intent by tying 'start'/'check'/'stop'/'list' to the action enum, but it does not meaningfully explain parameter details beyond the schema.

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?

States a specific function—monitoring a web page for content changes—and enumerates the four supported operations. This clearly distinguishes it from one-shot sibling tools like fetch_page, screenshot, and crawl.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies the monitoring workflow by listing start/check/stop/list, giving an agent clear operational context. However, it does not explicitly state when to choose this tool over siblings like fetch_page or crawl, and it offers no exclusions or alternative routing.

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

Deploy Server

Other Tools