Add takedown event
add_takedown_eventAppend an entry to a takedown's timeline. comment records progress or correspondence ('registrar replied, ticket #123') and carries no code; action logs a step the user performed and requires that step's catalog code, which must be one of the match's current possible next steps (get_match lists the suggested ones under actions; a rejected code's error names every step that applies). Steps only log on an open takedown; comments also work on closed ones. Entries are append-only: a mistaken one is retracted with retract_takedown_event, never edited.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"takedown_id": "<takedown_id>",
"type": "<type>",
"body": "<body>"
},
"name": "add_takedown_event"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | What happened, in plain text; for an action, a description of what was done. | |
| code | No | Required on action and rejected on comment: the catalog code of the step performed, e.g. report_registrar, from the match's current possible next steps. | |
| type | Yes | comment is a freeform note without code; action logs a performed step and needs code. | |
| takedown_id | Yes | Takedown id from list_takedowns. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| event | Yes |