Programación de una cuenta de Twitch MCP

1. Read The Returned Stream Schedule

Prompt: Retrieve the schedule for [Twitch handle] and list its returned stream titles, start times and end times. Preserve supplied timezone information and distinguish missing schedule data from an empty schedule. Do not assume additional pages can be fetched.

2. Find The Next Scheduled Stream

Prompt: Retrieve the schedule for [Twitch handle] and show the next segment identified by the response with its start time. Keep this planned event separate from a currently live stream, and report an absent next segment without inventing a schedule.

3. Check Schedule Cancellations And Interruptions

Prompt: Retrieve the returned schedule for [Twitch handle] and identify segments marked cancelled, any cancellation-until value, and schedule interruptions. Keep these separate from ordinary scheduled start times; do not assume a missing schedule means the streamer is offline.

4. Fit Scheduled Streams Into My Viewing Window

Prompt: For [Twitch handle], compare returned schedule segment start and end times against [my viewing window and timezone]. Convert only timestamps with an explicit offset and flag ambiguous times. Exclude segments marked cancelled, retain unknown end times, and do not promise future streams beyond the returned schedule.

What You Need to Provide

Use only the documented public inputs. Private, restricted, missing and partial results remain distinct; missing metrics are not zero.

Check the current Nexscope price before running the request. Optional enrichment, downloads, transcription and additional pages can incur charges. These examples do not execute a request.

Only the documented handle input is available here. The prose mentions pagination and trimming, but those inputs are absent from the published request contract.