Monitors

List the monitors this tenant is running

Every monitor you have created, with its definition and schedule — and without the callback secret.

list_monitors

What it is

The job: See what you are already watching, and what it is costing you per hour.

The inventory call. It returns each monitor’s definition — name, check type, URL, selector or watch spec, cadence, callback URL and active state — so you can audit what is running and what its recurring cost adds up to.

Callback secrets are excluded from the response. They are write-only by design: you set one at creation and verify signatures with your own copy.

The call

Call it exactly like this.

Copied from the tool's registration and the route handler — not paraphrased.

MCPlist_monitors.mcp.jsonjson

// MCP tool call — server "twin-browser"
{
  "tool": "list_monitors",
  "arguments": {}
}

GET /api/v1/monitorsrequest.shbash

curl -X GET "https://twin-browser.com/api/v1/monitors" \
  -H "Authorization: Bearer $TWIN_API_KEY"

Returns

response.jsonjson

{ "monitors": [ { "id": "…", "name": "pricing page", "check_type": "observe",
                  "url": "…", "interval_seconds": 3600, "active": true, … } ] }

What it costs

Free

A metadata read. The monitors themselves cost credits on each scheduled check; listing them does not.

See the full rate card

Which one

When a different tool is the right call.

The honest answer is often the neighbouring tool. These are the trades.

get_monitor_history

This tells you what is configured; history tells you what actually happened. A monitor that looks healthy in the list can still be erroring on every check.

get_monitor_history

Keep going

The rest of the tool set.

create_monitor

Know when something on a page changed, without polling it yourself.

get_monitor_history

Tell the difference between “nothing changed” and “the check has been broken for a week”.

delete_monitor

Turn off a watch you no longer need.

Get an API key All tools