set_message_importance
DestructiveIdempotent
Change only your message's low/normal/high/urgent priority. Requires current expected_revision from inbox, history or sender receipt and a nonempty idempotency_key. Returns message_id, revision, importance and changed.
Instructions
Change only your message's low/normal/high/urgent priority. Requires current expected_revision from inbox, history or sender receipt and a nonempty idempotency_key. Returns message_id, revision, importance and changed. A stale revision fails before a matching-value no-op. Edits affect metadata only: no new inbox notice or repeated instruction, and priority does not grant authority. Requires explicit server activation; identical retries replay before activation, lifecycle or revision checks.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| importance | Yes | low, normal, high or urgent. | |
| message_id | Yes | Message id. | |
| project_key | Yes | Absolute path of the repository's primary checkout. | |
| sender_name | Yes | Your registered agent name. | |
| idempotency_key | Yes | Nonempty key for this tool and agent. Identical arguments replay with idempotent_replay:true; different arguments fail with IDEMPOTENCY_KEY_CONFLICT. Cleanup runs at server startup and hourly, removing keys older than 7 days. Retries can replay until removal; afterward a retry may perform the operation again. | |
| expected_revision | Yes | Current message revision, initially 0; inspect metadata again after a conflict. |