Skip to main content
Glama

Create a watch-together room

create_watch_room

Creates a private ScreenParty room where friends watch the same video in sync, in their browsers, with chat and voice. Use it when the user wants to watch something together now, or plan a watch party at a set time. Without start_time the room is ready now: the first person to open room_link becomes the host (controls playback), so tell the user to open it before sharing. With start_time it returns a countdown page with "add to calendar" for guests; the room opens 15 minutes early, and organiser_link lets the user open it any time and host it. Share room_link or schedule_page with guests; keep organiser_link and organiser_key for the user only (they also change it with update_watch_party and cancel it with cancel_watch_party). The room made here is what the *_watch_party tools call a watch party — same room_code.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_watch_room"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoWhat people will watch, e.g. "Lesson 3: Past tense". Defaults to "Watch party".
video_urlNoOptional video the room opens with. A direct video link (mp4, webm, m3u8) or a public YouTube video URL. Paid streaming services are not supported.
start_timeNoOptional. ISO 8601 date-time WITH a time zone, e.g. 2026-11-07T20:00:00+08:00 (ask the user for their time zone if unknown). Omit for a room that opens now. Up to 60 days ahead.

Output Schema

NameRequiredDescriptionDefault
okYesfalse when the call failed; then code says why.
codeNoError code when ok is false.
opens_atNoISO time guests can enter (15 minutes before).
room_codeNo5-character room code.
room_linkNoLink guests open to join the room.
starts_atNoISO time it starts.
organiser_keyNoPrivate: needed to cancel with cancel_watch_party.
schedule_pageNoCountdown page with "add to calendar"; best link to share for a later party.
organiser_linkNoPrivate: opens the room as host, even before it opens to guests.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / start_time / description
      Previous value: -"Optional. ISO 8601 date-time with time zone, e.g. 2026-11-07T20:00:00+08:00. Omit for a room that opens now. Up to 60 days ahead."New value: +"Optional. ISO 8601 date-time WITH a time zone, e.g. 2026-11-07T20:00:00+08:00 (ask the user for their time zone if unknown). Omit for a room that opens now. Up to 60 days ahead."
    • changedInput schema / properties / title / description
      Previous value: -"What people will watch, e.g. \"Lesson 3: Past tense\"."New value: +"What people will watch, e.g. \"Lesson 3: Past tense\". Defaults to \"Watch party\"."
    • changedInput schema / properties / video_url / description
      Previous value: -"Optional. A direct video link (mp4, webm, m3u8) or a public YouTube video URL."New value: +"Optional video the room opens with. A direct video link (mp4, webm, m3u8) or a public YouTube video URL. Paid streaming services are not supported."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "code": {
      +      "description": "Error code when ok is false.",
      +      "type": "string"
      +    },
      +    "ok": {
      +      "description": "false when the call failed; then code says why.",
      +      "type": "boolean"
      +    },
      +    "opens_at": {
      +      "description": "ISO time guests can enter (15 minutes before).",
      +      "type": "string"
      +    },
      +    "organiser_key": {
      +      "description": "Private: needed to cancel with cancel_watch_party.",
      +      "type": "string"
      +    },
      +    "organiser_link": {
      +      "description": "Private: opens the room as host, even before it opens to guests.",
      +      "type": "string"
      +    },
      +    "room_code": {
      +      "description": "5-character room code.",
      +      "type": "string"
      +    },
      +    "room_link": {
      +      "description": "Link guests open to join the room.",
      +      "type": "string"
      +    },
      +    "schedule_page": {
      +      "description": "Countdown page with \"add to calendar\"; best link to share for a later party.",
      +      "type": "string"
      +    },
      +    "starts_at": {
      +      "description": "ISO time it starts.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "ok"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare non-readonly, non-destructive, non-idempotent, open-world; the description adds substantial behavior the agent could not otherwise know: first opener becomes host, scheduled rooms open 15 minutes early, organiser_link lets the creator host at any time, and organiser_key/organiser_link must be kept private while room_link/schedule_page are shared. This is exactly the kind of auth/ownership and side-effect disclosure the annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and then branches cleanly into the now-vs-scheduled behavior, with zero filler sentences. It is a dense single block that would read faster with explicit bullets for the link-sharing rules, but no sentence is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the full decision surface for a three-optional-parameter creation tool: what is created, the two modes, who becomes host, what links are returned and which to share. With an output schema present it need not document return payloads, so nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns extra by explaining the semantic consequence of the optional start_time (omit = room live now with host-by-first-arrival; present = countdown page with calendar add and early open). It does not add much for title or video_url beyond the schema, so it stops short of 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Creates a private ScreenParty room") and immediately defines the scope: synchronized video playback with chat and voice in browsers. It also explicitly ties itself to the sibling family by noting "The room made here is what the *_watch_party tools call a watch party — same room_code," so an agent can place it among get/update/cancel siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use framing ("when the user wants to watch something together now, or plan a watch party at a set time") and branches the two modes on start_time. It names the alternatives and their roles — update_watch_party for changes, cancel_watch_party for cancellation — leaving little to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources