Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

monitors_checks

List a monitor's recent check history, including webhook delivery status per run, to inspect the last 50 runs newest first.

Instructions

List a monitor's check history. Returns the caller's own monitor's most recent check runs (most recent first, capped at 50), including webhook delivery status per run.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMonitor ID returned by your account monitor create/list response; replace the illustrative example with your own ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.9
    • changedInput schema / properties / id / description
      Previous value: -"Monitor id"New value: +"Monitor ID returned by your account monitor create/list response; replace the illustrative example with your own ID"
  2. Addedv1.16.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does well: it discloses ordering (most recent first), a hard cap (50 results), an ownership restriction ('caller's own monitor'), and the per-run content (webhook delivery status). It stops short of stating pagination behavior beyond the cap or any auth/rate-limit constraints.

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?

Two tight sentences with zero filler. The primary purpose is front-loaded, and the second sentence carries only the return-shape information an agent needs to interpret results.

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 one-parameter read tool with no output schema, the description supplies the return semantics (ordering, cap, per-run fields) that would otherwise be missing. Remaining gaps are minor — no statement of what happens past the 50-cap or how 'delivery status' values should be interpreted.

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% and the single 'id' parameter is already documented as the monitor ID from the create/list response. The description adds nothing about the parameter format beyond what the schema provides, so the baseline of 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 ('List a monitor's check history') with clear scope — the caller's own monitor, not all monitors. This distinguishes it from sibling read tools like monitors_get (monitor metadata) and monitors_list (all monitors). An agent can route to it without opening the schema.

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?

Usage is implied by the resource ('check history' clearly maps to a diagnostic/inspection need), but there is no explicit when-to-use or when-not-to-use guidance versus siblings such as monitors_get or monitors_update. No prerequisites or alternative routing are stated.

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

Deploy Server

Other Tools