Skip to main content
Glama

Get page watch results

get_watch
Read-onlyIdempotent

Get the state of a page watch created with watch_page: last check, HTTP status, number of changes, and the most recent diffs with changed sections and keyword events.

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": {
      "id": "<id>"
    },
    "name": "get_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWatch id returned by watch_page.
historyNoNumber of recent changes to return (default 5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / history / description
      Previous value: -"Number of recent changes to return (default 5)"New value: +"Number of recent changes to return (default 5)."
    • changedInput schema / properties / id / description
      Previous value: -"Id returned when the job was created"New value: +"Watch id returned by watch_page."
  2. Changed1 schema field changed
    • addedInput schema / properties / history
      Added value: +{
      +  "description": "Number of recent changes to return (default 5)",
      +  "maximum": 10,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  3. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety is covered. The description adds genuine value by detailing the returned payload shape (last check, status, change count, diffs, keyword events), which annotations cannot express. It omits what happens for an unknown or expired watch id, which keeps it from a 5.

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?

A single front-loaded sentence with the action first and the return contents trailing. No filler, no restatement of the title, every clause carries information.

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 no output schema, the description correctly takes on the burden of listing return fields, which it does thoroughly. The only shortfall is edge-case behavior (invalid id, watch not yet checked), which matters for a polling-style retrieval tool but is minor given the annotations.

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%: id is documented as "Watch id returned by watch_page" and history as the count of recent changes with default and bounds. The description adds nothing about either parameter, so the baseline 3 applies since the schema does all the work.

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?

Specific verb and resource ("Get the state of a page watch") plus an enumeration of exactly what comes back: last check, HTTP status, change count, recent diffs with changed sections and keyword events. Naming watch_page as the creator anchors it in the lifecycle and separates it from the creation tool.

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 phrase "created with watch_page" implies this is the read-back step after creating a watch, which is useful context. But there is no explicit when-to-use guidance versus siblings like check_watch_now or stop_watch, and no statement that this only reads existing state without triggering a new check.

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.