Skip to main content
Glama
Sign In

Hoot Lens

by com.hootlens
OverviewDiscussionsAdmin

List logged changes

list_changes
Read-only

Lists logged changes (change markers), newest first: what changed, when, and for which page group. Includes changes logged through the API by agents, changes the owner logged, and changes Hoot Lens detected automatically when a page's content changed (source starts with "auto:"). Each has an id. pageGroup also returns site-wide changes.

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": {
      "projectId": "<projectId>"
    },
    "name": "list_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLatest change time, epoch milliseconds
fromNoEarliest change time, epoch milliseconds
pageGroupNoA page group id or name, or a path such as /pricing
projectIdYesThe project ID

Output Schema

NameRequiredDescriptionDefault
changesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavior beyond that: newest-first ordering, the three change-source categories, the 'auto:' source prefix convention, that each change carries an id, and that pageGroup widens results to site-wide changes.

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 action and ordering, then the source taxonomy, then the pageGroup caveat. Every sentence carries information; the 'auto:' detail is arguably verbose but it defines a real data convention an agent will encounter.

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?

For a read-only list tool with full schema coverage and an output schema, the description covers the essentials: what is listed, ordering, source categories, and the pageGroup scope quirk. Nothing about calling it correctly is missing, though filtering/pagination expectation is left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the schema already documents from/to as epoch milliseconds and pageGroup as an id/name/path. The description contributes extra meaning by explaining that pageGroup also returns site-wide changes, which the schema text does not convey.

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 ('Lists logged changes (change markers)'), plus ordering ('newest first') and returned fields ('what changed, when, and for which page group'). No sibling tool overlaps with change-log listing, so no differentiation is needed.

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 when this is useful by enumerating the three change sources (agent API changes, owner changes, auto-detected changes) and noting site-wide changes, but it never says when to reach for this tool versus alternatives like change_impact or weekly_summary, and gives no exclusions.

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

All Hoot Lens toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources