Report a thread as spam
report_spamMoves a thread of a mailbox into its Spam folder, where it stays readable and can be taken back out, and blocks its sender: their next message is filed in Spam too, without anybody being asked again. Spam is emptied 30 days after a thread lands there by default, or after the retention set on the account, and that deletion is final. Threads of a helpdesk queue have no Spam folder and are refused: file_conversation with "trash" throws them away instead. To report several threads, give conversation_id the list of their ids, in ONE call rather than one call per thread: the answer then lists in "results" the outcome of each thread in the order given ("ok", with its "result" or its "error") and counts "succeeded" and "failed". Each thread passes exactly the checks it would alone, so one refused or out of reach ("not found") leaves the others done, and the call is an error only when none succeeded.
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": {
"conversation_id": "<conversation_id>"
},
"name": "report_spam"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| conversation_id | Yes | The id of the conversation, as list_conversations gives it, or a list of up to 50 ids to do the same to every one of them in a single call. |