delete · mentions:write
Delete a view
Delete a view
WriteDestructiveIdempotent
REST
delete
/api/v1/views/{id}curl "https://herculeradar.com/api/v1/views/:id" \ --request DELETE \ --header "Authorization: Bearer hr_live_…"
MCP
Tool name delete_mention_view. It takes the same input and returns the same { data, meta } envelope as REST, because both call the same function.
Delete a saved view. The mentions it pointed at are unaffected.
Parameters
| idrequired | string | View id |
Response
{
"data": {
"deleted": true,
"id": "uuid"
},
"meta": {
"capability": "delete_mention_view",
"requestId": "req_9f2b4a8c1d0e",
"idempotencyReplayed": false,
"docs": "https://herculeradar.com/docs/reference/delete_mention_view"
}
}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.