List keywords

curl "https://herculeradar.com/api/v1/keywords" \
  --header "Authorization: Bearer hr_live_…"

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

Flattened keyword list across monitors. Prefer this when the user talks in keywords, not monitors.

{
  "data": {
    "keywords": [
      {
        "keyword": "Acme",
        "monitor_id": "uuid"
      }
    ]
  },
  "meta": {
    "capability": "list_keywords",
    "requestId": "req_9f2b4a8c1d0e",
    "idempotencyReplayed": false,
    "docs": "https://herculeradar.com/docs/reference/list_keywords"
  }
}

Requires the monitors:read 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.