post · mentions:write

Mark coincidental

Sets is_relevant false and status ignored.

Write

REST

post/api/v1/mentions/{id}/irrelevant
curl "https://herculeradar.com/api/v1/mentions/:id/irrelevant" \
  --request POST \
  --header "Authorization: Bearer hr_live_…"

MCP

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

The keyword match was coincidental. Sets is_relevant=false and status=ignored so analytics stop counting it as about you.

Parameters

idrequiredstringMention id

Response

{
  "data": {
    "id": "uuid",
    "is_relevant": false,
    "status": "ignored"
  },
  "meta": {
    "capability": "mark_mention_irrelevant",
    "requestId": "req_9f2b4a8c1d0e",
    "idempotencyReplayed": false,
    "docs": "https://herculeradar.com/docs/reference/mark_mention_irrelevant"
  }
}

Authorization

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