Try it

delete · monitors:write

Delete a keyword group

Delete a keyword group

WriteDestructiveIdempotent

REST

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

MCP

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

Drop the label. Keywords filed under it become ungrouped; mentions stay.

Parameters

idrequiredstringGroup id

Response

{
  "data": {
    "deleted": true,
    "id": "uuid"
  },
  "meta": {
    "capability": "delete_keyword_group",
    "requestId": "req_9f2b4a8c1d0e",
    "idempotencyReplayed": false,
    "docs": "https://herculeradar.com/docs/reference/delete_keyword_group"
  }
}

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