Skip to main content
Glama

Monitor a new page

add_source
Idempotent

Start monitoring a web page for the user. One page per URL: if the account already monitors this URL — under any instructions — no second page is started. The settings this call carries are applied to the page that already exists instead, and the response says which case you got: created is true for a new page, false for one that was already monitored, where updatedSettings lists what this call changed on it. Each check spends one credit per page it reads — the source page, plus each item page it follows.

Input Schema

NameRequiredDescriptionDefault
urlYesThe page URL to monitor.
userPromptNoOptional instructions for what changes matter. On a page already monitored this replaces its instructions; pass null to clear them. A changed prompt there re-learns how the page is read: one credit if the re-learn succeeds, skipped at zero balance (the prompt still saves).
monitoringFrequencyNoMinutes between checks, from 30 to 10080; anything outside that range is refused rather than quietly changed. Checks run on a scheduler tick, so the cadence actually in effect can be slower than the one stored — read `effectiveMonitoringFrequency` from get_source or list_sources for it. Defaults to 60.
notificationsEnabledNoWhether to notify on changes (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the upsert behavior, the response discriminator (`created` true/false and `updatedSettings`), and the credit cost per check including followed item pages. An agent knows exactly what will happen and what it will cost before calling.

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?

Four sentences, front-loaded with the action, then the dedupe rule, then the response shape, then cost. No sentence is redundant and each one answers a question an agent would otherwise have to guess at.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by explaining the return discriminator and the `updatedSettings` field. Combined with the schema's parameter docs and the cost model, an agent has enough to invoke correctly and interpret the result.

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 every parameter is already documented with range, defaults, and null semantics in the schema itself. The description adds no parameter-level detail beyond that, which is the expected baseline when the schema carries the load.

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 ('Start monitoring a web page') and immediately clarifies the non-obvious semantic: one page per URL, with settings merged into an existing page. This implicitly separates it from update_source, though no sibling is named explicitly.

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 critical usage condition is spelled out — calling this on an already-monitored URL does not duplicate, it updates — which is what an agent most needs to know before invoking. It stops short of naming alternatives like update_source for pure settings changes or pause/resume for lifecycle control.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources