> ## Documentation Index
> Fetch the complete documentation index at: https://docs.keenable.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Every page is listed in https://docs.keenable.ai/llms.txt. To pick a product for a job, read https://docs.keenable.ai/choose.md
> Setup steps for agents, covering the SDKs, the MCP server and the CLI: https://docs.keenable.ai/skill.md
> Keenable search and fetch work without an API key. To add them to code, use the official SDK for the project's language: https://docs.keenable.ai/sdks.md
> Without a key, call POST https://api.keenable.ai/v1/search/public or GET https://api.keenable.ai/v1/fetch/public with an X-Keenable-Title header that names your app.
> With a key, send it in the X-API-Key header and read it from the KEENABLE_API_KEY environment variable. Never ask a user to paste a key into chat. Every access method: https://docs.keenable.ai/auth.md
> To get an API key without the console, use device login: https://docs.keenable.ai/authentication.md#device-login
> MCP server: https://api.keenable.ai/mcp (no key, or X-API-Key; keyless Codex uses https://api.keenable.ai/mcp-public), or https://api.keenable.ai/mcp-oauth for OAuth sign-in. These docs are an MCP server at https://docs.keenable.ai/mcp and the OpenAPI spec is at https://docs.keenable.ai/api-reference/openapi.json
> Keenable searches and fetches public web pages. If a question needs no web information, skip the call.
> On 402 with an API key (code insufficient_credits), stop and ask a human to add credits; don't retry. On 429, wait the number of seconds in Retry-After, then retry. Before you ship, follow https://docs.keenable.ai/production.md
> Every error, with its cause and fix, is in https://docs.keenable.ai/errors.md and moving from another search API is covered in https://docs.keenable.ai/migrate.md
> Before you compare Keenable with another search API, read https://docs.keenable.ai/guides/evaluate-search-apis.md

# Four Monitors tools over MCP

> Released 18 November 2026: the MCP server lists four Monitors tools, and get_monitor_results replaces whats_new and monitor_pages.

Released 18 November 2026. With an API key or a Keenable sign-in, the [MCP server](https://docs.keenable.ai/mcp-server.md#monitors-tools) lists four Monitors tools: `create_monitor`, `list_monitors`, `get_monitor_results` and `delete_monitor`. One tool, `get_monitor_results`, now reads both new and earlier results, so your agent picks from four Monitors tools instead of nine.

If a scheduled task or a prompt names `whats_new` or `monitor_pages`, change it to `get_monitor_results`. The old names still run, so nothing breaks while you switch.

## What changed

| Before 18 November | From 18 November | What to do |
| - | - | - |
| `whats_new` | `get_monitor_results` | Rename the tool. The arguments are the same: `monitorId`, `minImportance`, `limit`, `reader` and `peek`. |
| `monitor_pages` with `id` | `get_monitor_results` with `monitorId` and `includeSeen: true` | Rename the tool, rename `id` to `monitorId` and add `includeSeen: true`. A page holds up to 50 results instead of 100. |
| `get_monitor`, `update_monitor`, `trigger_monitor`, `get_run` | Not listed | Use the [Monitors API](https://docs.keenable.ai/api-reference/monitors/create.md), an [SDK](https://docs.keenable.ai/sdks.md) or the [CLI](https://docs.keenable.ai/cli.md#monitors) to read, pause, change or run a monitor. |
| `create_monitor`, `list_monitors`, `delete_monitor` | Unchanged | Nothing. |

`tools/list` no longer names the six old tools. A client that calls one of them by name, for example from a cached tool list, still gets an answer as before.

`get_monitor_results` keeps the reader's place from `whats_new`. A scheduled task that switches tools doesn't get the same results twice, and it doesn't skip any.

## Call get\_monitor\_results directly

The MCP server answers a single `POST` with no session, so you can test a tool call with curl. This request asks for the results of one monitor that this reader hasn't been given yet, rated 4 or higher:

```bash theme={"theme":{"light":"github-light-high-contrast","dark":"dark-plus"}}
curl https://api.keenable.ai/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-API-Key: $KEENABLE_API_KEY" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "get_monitor_results",
      "arguments": { "monitorId": "mon_3kq9z2c8f1a04b7d9e6f5a21", "minImportance": 4, "peek": true }
    }
  }'
```

Replace the `monitorId` with one from `list_monitors`, or leave it out to read every monitor. `peek: true` leaves the results unread, so a test call doesn't use up results your scheduled task should get. You get a JSON-RPC response. Its `result.structuredContent` holds the tool's answer, and `result.content[0].text` holds the same answer as a string.

The shape of the answer depends on whether you send `includeSeen`:

| Call | Answer fields | Next page |
| - | - | - |
| Without `includeSeen` | `results`, oldest first, plus `count`, `hasMore` and `monitors` | If `hasMore` is `true`, call the tool again. |
| With `includeSeen: true` and `monitorId` | `results`, newest first, plus `nextCursor` | Pass `nextCursor` as `cursor`. |

`whats_new` returned its list under `pages`, and `monitor_pages` returned it under `data`. If your code reads the tool's answer, read `results` instead.

## Update a scheduled task

If a scheduled task in Claude or ChatGPT names the old tool, edit its prompt to name the new one:

```text theme={"theme":{"light":"github-light-high-contrast","dark":"dark-plus"}}
Every hour: call get_monitor_results on Keenable. If it returns results, tell me about them
in a few lines, the most important first, with links. If it returns none, say nothing.
```

The next run calls `get_monitor_results` and continues from where `whats_new` stopped.

## Related

* [Monitors tools](https://docs.keenable.ai/mcp-server.md#monitors-tools): every argument of the four tools.
* [Monitors](https://docs.keenable.ai/products/monitors): webhooks, schedules and limits.
* [Changelog](https://docs.keenable.ai/changelog.md): every change, newest first.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.