monity.ai

List monitors

list_monitors

Read-only

List the website monitors (tasks) in the monity.ai account: name, monitored URL, type, active state, labels, and last/next check times. Use this first to find a monitor's uuid for the other tools.

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": "list_monitors"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (default 1)
`sort`	No	Task list sort order; default newest created
`label`	No	Filter by label name
`limit`	No	Results per page (default 25, max 100)
`active`	No	Filter by active state
`search`	No	Search monitor name or URL, case insensitive
`labelIds`	No	Only monitors carrying one of these labels (ids from list_labels)
`createdOn`	No	Only monitors created on this date (yyyy-mm-dd, UTC)
`thresholds`	No	Only monitors with one of these change thresholds
`frequencies`	No	Only monitors checking at one of these frequencies (minutes, as strings)
`lastAlertTo`	No	Only monitors whose last change is on or before this ISO date
`workspaceId`	No	Only monitors in this workspace (from list_workspaces)
`compareTypes`	No	Only monitors of these compare types
`lastAlertFrom`	No	Only monitors whose last change is on or after this ISO date

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4/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 the safety profile is covered. Beyond that the description enumerates the attributes the account returns, which is useful since no output schema exists; it omits pagination behavior (default 25, max 100) that would matter operationally.

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 sentences, zero filler, with the scope and returned fields front-loaded before the workflow instruction. Every clause earns its place.

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 14-parameter, zero-required list tool with no output schema, the description supplies the return shape and the reason to call it first, which is the essential context. Minor gaps remain around pagination and the filter set, both of which the schema does cover adequately.

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 all 14 parameters are self-documenting and the baseline is 3. The description adds no meaning about the substantial filtering surface (labels, workspaces, date ranges, sort), so an agent relying on prose alone would not know these capabilities exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List the website monitors (tasks)') plus the account scope and the fields returned (name, URL, type, active state, labels, check times). It implicitly separates itself from get_monitor by framing itself as the discovery step, though it never names the sibling it is not.

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

Usage Guidelines4/5

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

'Use this first to find a monitor's uuid for the other tools' gives an explicit workflow position and tells the agent why it would pick this over get_monitor. It stops short of stating when-not to use it or pointing at alternatives for filtered/single-monitor retrieval.

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

All monity.ai tools Inspect

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

Need Help?