Cancel the subscription
amber_cancel_subscriptionCancel a user's PayPal subscription with confirmation, preserving data and access until the next billing date; use account deletion only if the entire account must be removed.
Instructions
Cancel the user's PayPal subscription. Access continues until next_billing_date (already paid). Data is preserved, not deleted. Do NOT use if the user wants to delete their account entirely -- use amber_delete_account instead.
Cancellation is sent to PayPal immediately; status update arrives via webhook within ~1 minute. Returns code: no_subscription if none exists. Requires confirm: true.
Errors: cancelled (you did not pass confirm: true; NOTHING was attempted - the name is historical and collides with the success status: cancelled this same tool returns when a cancellation DOES happen, so branch on which FIELD carried it: error.code means you did not confirm, status means it is done), no_subscription (this account has no subscription), not_found (PayPal did not recognise the subscription id on this account; it may already have been cancelled or expired), deletion_scheduled (the account is already scheduled for deletion, which ends billing anyway), cancel_failed (PayPal refused; the subscription is unchanged, so it is safe to retry).
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": {
"confirm": "<confirm>"
},
"name": "amber_cancel_subscription"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| confirm | Yes | When `true`: cancels the subscription on PayPal and updates account status. When `false`: returns `code: cancelled` with no side effects, letting you confirm intent first. A STRINGIFIED boolean is also accepted (`"true"`, `"TRUE"`, `" true "`), because some clients JSON-stringify every argument and would otherwise be unable to cancel at all; the published type is `boolean` because that is what a client should send. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| status | Yes | Always `cancelled`. Access continues to the end of the paid period rather than stopping now, and memories are preserved either way. | |
| message | Yes | A human-readable summary, including when access actually ends. |