Skip to main content
Glama

Track a page and let people follow it (preview)

create_public_tracker

Creates a monitor and returns a public-sharing preview so you can review and approve details before publishing a public tracker.

Instructions

Step 1 of 2 for "track X and let people subscribe" (needs an API key with the write and network:publish scopes): creates the monitor (as create_monitor does: plan limits apply, the first check starts now) and returns exactly what would become public on Monity Network (preview.shares, preview.doesNotShare), whether it can be public, public trackers of the same page (samePage), and a revisionId. Nothing is public yet: show the person the preview, get their agreement, then call publish_tracker with monitorUuid and revisionId. Call find_existing_network_watch first: if a public tracker already checks this page the same way, follow it instead.

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": {
      "websiteUrl": "<websiteUrl>"
    },
    "name": "create_public_tracker"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoMonitor name (defaults to the URL host/path); also the public title unless title is given
scopeNoWhat exactly it covers, e.g. "UK store, size 10"
titleNoPublic title (default: the monitor name)
categoryNoA topic, e.g. deals, tickets, tech, jobs
keywordsNoTEXT monitors only: comma-separated keywords to look for
selectorNoCSS selector of ONE element to check instead of the whole page, e.g. '.product-price'
frequencyNoMinutes between checks, as a string: '60' (hourly), '1440' (daily)… Omit for the plan default
notifyWhenNoThe alert condition in words, e.g. 'when it is back in stock'
websiteUrlYesAbsolute http(s) URL of the public page to track
compareTypeNoComparison mode (default AUTO)
descriptionNoWhy it is worth following
workspaceIdNoWorkspace for the monitor (from list_workspaces); defaults to the key owner's personal workspace
keywordsActionNoTEXT monitors only: alert when keywords are ADDED (default) or REMOVED

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses that plan limits apply, that the first check starts immediately, that nothing becomes public yet, and that the response contains preview.shares, preview.doesNotShare, samePage and a revisionId. The auth scope requirement and the non-destructive preview semantics are exactly the behavioral context an agent needs.

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?

Front-loaded with the step framing and the key constraint ('Nothing is public yet'), and every sentence carries actionable information. It is dense and packs several ideas into one paragraph with nested quotes, which slightly hurts scannability, but there is no filler.

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?

For a 13-parameter creation tool with no output schema and no annotations, the description covers the gaps that matter: what is returned, that the operation is a preview rather than a publish, the auth scopes, and the required follow-up call. Nothing an agent needs to invoke it correctly is missing.

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 every one of the 13 parameters is already documented in the schema, which sets the baseline at 3. The description adds no parameter-level detail beyond noting the tool behaves 'as create_monitor does'; the monitorUuid and revisionId it mentions are outputs, not inputs.

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 verb and resource ('creates the monitor') and explicitly frames itself as step 1 of 2 in a two-call flow, distinguishing it from create_monitor (same creation semantics) and publish_tracker (the follow-up). An agent can tell exactly what this tool produces: a preview plus a revisionId, not a live public tracker.

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

Usage Guidelines5/5

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

Gives explicit sequencing: call find_existing_network_watch first and follow an existing tracker if one matches, then show the preview and get agreement, then call publish_tracker with monitorUuid and revisionId. It also names the required API key scopes, which is a precondition an agent must check before invoking.

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