# create-keyword-monitor

Create a KEYWORD monitor that fetches a URL and alerts when a given keyword appears (or is missing) in the response body.

Skill by UptimeRobot. Category: Shipping and ops.

## Install

Project (for this project only):

```sh
npx skills add uptimerobot/ai --skill create-keyword-monitor
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

Global (for every project on this machine):

```sh
npx skills add uptimerobot/ai --skill create-keyword-monitor -g
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

## Tags

- Runs on your computer: It runs as a program on your machine, with your access.

## Security audits

- Gen Agent Trust Hub: Pass
- Socket: Pass
- Snyk: Pass

Installs: 10. Installs counted by skills.sh. [Open on skills.sh](https://www.skills.sh/site/uptimerobot.ai/create-keyword-monitor)

## Source

[Open the source](https://github.com/uptimerobot/ai/tree/HEAD/skills/create-keyword-monitor). Checked 2026-10-10. This summary may contain AI-generated text, so it can be wrong. Check the source before you rely on it.

## SKILL.md

````markdown
---
name: create-keyword-monitor
description: Create a KEYWORD monitor that fetches a URL and alerts when a given keyword appears (or is missing) in the response body.
tags: [monitoring, keyword, content-check, create, uptimerobot]
---

# Create a KEYWORD monitor

> **Preflight — read first.** If you cannot see any `uptimerobot:*` MCP tools in your tool list, invoke the `uptimerobot:setup` skill before doing anything else. Do not tell the user the MCP is misconfigured — `setup`'s Step 0 detects the common case (server connected, tools loaded after session start) and resolves it without re-keying.

Use when the user cares not just that an endpoint returns a 200, but that a specific string is present (login page has "Sign in") or absent (homepage is not showing "502 Bad Gateway"). For structured JSON assertions, prefer `create-api-monitor` instead.

**Tool:** `create-monitor`
**Required params:** `friendlyName`, `type: "KEYWORD"`, `url` (full URL), `keywordValue`, `keywordType`.

## Minimal call

```json
{
  "friendlyName": "Login page shows Sign in",
  "type": "KEYWORD",
  "url": "https://app.example.com/login",
  "keywordValue": "Sign in",
  "keywordType": "ALERT_NOT_EXISTS"
}
```

`keywordType`:

- `ALERT_NOT_EXISTS` — alert when the keyword **disappears** (expected content missing → down).
- `ALERT_EXISTS` — alert when the keyword **appears** (error string present → down).

## Common optional params

All HTTP-monitor params are supported: `httpMethodType`, `authType`, `httpUsername`, `httpPassword`, `followRedirections`, `checkSSLErrors`, `timeout`, `interval`, `sslExpirationReminder`, `domainExpirationReminder`, `responseTimeThreshold`, `assignedAlertContacts`, `tagNames`, `maintenanceWindowsIds`.

KEYWORD-specific:

- `keywordCaseType` — `0` for case-sensitive (default), `1` for case-insensitive.

## Example: alert when a 500 message appears

```json
{
  "friendlyName": "Homepage not erroring",
  "type": "KEYWORD",
  "url": "https://www.example.com/",
  "keywordValue": "Internal Server Error",
  "keywordType": "ALERT_EXISTS",
  "keywordCaseType": 1,
  "interval": 60,
  "assignedAlertContacts": [
    { "alertContactId": "10", "threshold": 0, "recurrence": 0 }
  ]
}
```

## Common mistakes

- Leaving off `keywordType` — it is required.
- Using an HTTP monitor when the user said "alert me if the page shows X" — use KEYWORD.
- Case-sensitivity confusion. Default is case-sensitive; pass `keywordCaseType: 1` for insensitive.
- `keywordValue` longer than 500 chars is rejected.
- HEAD requests cannot match body content. If `httpMethodType` is `HEAD`, the keyword check will not work as expected.

## After creation

Call `get-monitor-details` to confirm `keywordValue`, `keywordType`, and `keywordCaseType` are stored correctly.

## Related

- `create-http-monitor` — if only status code matters.
- `create-api-monitor` — for JSON/XML response assertions.
````

- Previous: [create-http-monitor](https://syn4pse.dev/terminal/uptimerobot-create-http-monitor.md)
- Next: [create-ping-monitor](https://syn4pse.dev/terminal/uptimerobot-create-ping-monitor.md)
- [Terminal](https://syn4pse.dev/terminal.md)
- [Suggest a change](mailto:terminal@syn4pse.dev?subject=Terminal%20suggestion)
