remind_pass_window_queue
Nudge everyone who bought a window but has not come through their grant yet, re-sending it. Messages real people.
A pass holder who bought a window still has to come through their grant (on Telegram, tap the invite link and send a join request) before the window opens; the ones who have not are the window's queue. This tool re-sends the grant to every holder still in that queue, the way the dashboard's "remind everyone" action on a window does, and answers with how many holders the connector accepted the message for.
A window that has ended or been cancelled has nobody left to remind and answers 0. Holders who
already queued are skipped.
This messages real people
Confirm with the creator before calling, and do not repeat it within the same
window — the queue does not change because it was nudged twice. To remind one
holder, use remind_pass_holder.
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Runs the same action as
The REST endpoint and this tool share one action, so validation, permissions and events are identical.
Annotations
A client that honours annotations asks a person before running it. Sending the same arguments twice changes nothing the second time.
Arguments
project_id*stringUUID of the project whose pass plans own the window.
window_id*stringUUID of the window whose missing holders to nudge.
What it returns
{ "data": { "window_id": "3d5a8c72-b016-4e94-8fa7-61c209d4e738", "reminded": 4 }}reminded counts messages the connector accepted, not holders in the queue: a holder who has blocked
the bot is in the queue but cannot be reached, and is not counted.
How it fails
VALIDATION_FAILEDthe reminder was refused for the window's current state.
RESOURCE_NOT_FOUNDunknown project_id or window_id, a window of another project, or a project outside the token's scope.
AUTHENTICATION_REQUIREDno authenticated user on the request.
TOKEN_MISSING_ABILITYtoken lacks pass-window:update.
How is this guide?
Last updated on