Version
WRITE

remind_member_to_connect

Remind one member that a place of their purchase still waits for an account they have not connected, with the door that connects it. Answers whether anything was sent.

The members flyout's Remind to connect, for agents. A member who bought a plan with a place on a platform they have not connected (a Discord role bought through the Telegram bot, say) holds that place as waiting until they connect the account. This sends them one reminder, by mail and in the chat their connected account reaches, with the door that connects it. Find the candidates with list_subscribers and access: waiting.

reminded: false is a normal answer, not an error. It means there was nothing to send: no place of the purchase waits, the member was reminded within the last day, they stopped the project's follow-ups, or the purchase has ended. It is the dashboard's "Nothing Sent" notice. The daily reminder already nudges every waiting member once on its own, a day after the purchase or a day before the pass window opens; this is the creator's own press on top of it.

This messages a real person

Read the member back with list_subscribers and access: waiting first. A second press within a day sends nothing, so there is no point repeating it.

The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.

The REST endpoint and this tool share one action, so validation, permissions and events are identical.

Annotations

Idempotent

Sending the same arguments twice changes nothing the second time.

Arguments

subscription_id*string

UUID of the purchase whose place waits for an account.

What it returns

{  "data": {    "subscription_id": "5b7e2d40-1a86-4c39-97f2-e83d0b16c5a4",    "reminded": true  }}

How it fails

RESOURCE_NOT_FOUND

unknown subscription_id, or a subscription outside the token's scope.

AUTHENTICATION_REQUIRED

no authenticated user on the request.

TOKEN_MISSING_ABILITY

token lacks project-subscription:update.

How is this guide?

Last updated on