Try it

delete · monitors:write

Stop tracking a term

id is the keyword string. Soft-stops the monitor if it was the last term.

WriteDestructiveIdempotent

REST

delete/api/v1/keywords/{id}
curl "https://herculeradar.com/api/v1/keywords/:id" \
  --request DELETE \
  --header "Authorization: Bearer hr_live_…"

MCP

Tool name delete_keyword. It takes the same input and returns the same { data, meta } envelope as REST, because both call the same function.

Stop tracking one term. The last term on a monitor soft-stops it; collected mentions keep their monitor_id.

Parameters

idrequiredstringKeyword

Response

{
  "data": {
    "deleted": true,
    "keyword": "Acme"
  },
  "meta": {
    "capability": "delete_keyword",
    "requestId": "req_9f2b4a8c1d0e",
    "idempotencyReplayed": false,
    "docs": "https://herculeradar.com/docs/reference/delete_keyword"
  }
}

Authorization

Requires the monitors:write scope. A credential without it gets 403 FORBIDDEN. Resources in projects the credential cannot reach answer 404 NOT_FOUND rather than 403, so ids cannot be probed across tenants.

Send an Idempotency-Key header. A completed response is replayed for 24 hours, so a retry after a timeout cannot create a duplicate.

REST conventionsMCP setupErrors & limits