Skip to main content
Glama

Get recent changes across all monitors

get_recent_changes

Retrieve an account-wide feed of completed checks, newest first, with monitor details, AI change summaries, and extracted output to answer reporting questions like what changed this week in one call.

Instructions

Account-wide feed of completed checks, newest first, each already carrying its monitor (name + URL), the AI summary of what changed, and the extracted output. This is the tool to use for reporting questions — 'what changed this week?', 'summarise my monitors', 'which pages moved?' — because it answers them in ONE call. Do not loop get_check_history over every monitor for that. Defaults to alerts only; set alertedOnly false to include no-change runs as a data feed. pageAccess says what the browser reached; when reachedContent is false the check saw a challenge, login or error page, so report that, not a change in content.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_recent_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoISO date upper bound (inclusive)
fromNoISO date lower bound, inclusive — e.g. last week's date for a weekly report
pageNoPage number (default 1)
labelNoOnly monitors carrying this label
limitNoResults per page (default 25, max 100)
statusNoExplicit status filter: ALERT_SENT, CHANGE, NO_CHANGE or ERROR. Ignored when alertedOnly is true.
alertedOnlyNotrue (default) returns only checks that detected a change and alerted; false returns every completed check
monitorUuidNoRestrict to a single monitor (from list_monitors)
includeHiddenNoInclude changes the user hid (hide_change). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses ordering (newest first), the default filter (alerts only) and how to widen it, and the fact that each row is pre-joined with its monitor and AI summary — saving an N+1 fetch. It stops short of covering pagination limits or what a NO_CHANGE row looks like, but the essential behavioral context is present.

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 core purpose and the sibling exclusion, and every clause is load-bearing, including the query examples that make the intent concrete. It is dense to the point of run-on in the final sentence about pageAccess and reachedContent, which could be split for readability.

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?

There is no output schema, so the description must describe returns, and it does: monitor name and URL, AI summary of the change, extracted output, and how to interpret pageAccess/reachedContent as a blocked-vs-changed signal. Missing details about pagination totals or total result counts are minor for a feed tool.

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 already 100%, so the schema documents all nine parameters itself. The description adds only marginal meaning — recasting alertedOnly=false as a 'data feed' and pushing the from/to range toward reporting — while the status/alertedOnly interaction is already spelled out in the schema. Baseline 3 applies.

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 ("Account-wide feed of completed checks, newest first") plus the payload each row carries. It also explicitly distinguishes itself from get_check_history, so an agent can pick correctly without opening either schema.

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?

Names the exact class of questions it is for ('what changed this week?', 'summarise my monitors') and adds an explicit anti-pattern: do not loop get_check_history over every monitor. It also explains the alternative mode (alertedOnly false) as a data feed.

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