Skip to main content
Glama

update_game

Idempotent

Needs sign-in (connect this server with OAuth, or pass an API key as the Authorization: Bearer header). Ships a new build of a game the creator already published, as its next version: same link, same origin, scores and comments kept. Needs the creator's API key. Stage with upload-build.mjs --from <this game's slug> so only changed files are sent. Stage a local build folder with Node 22+: download https://yougame.co/upload-build.mjs, then run node upload-build.mjs with YOUGAME_URL=https://yougame.co and YOUGAME_UPLOAD_TOKEN (from upload_token) or YOUGAME_API_KEY set. It applies the website's path fixes locally and streams files through POST /api/upload/start, PUT /api/upload/file (a file over 100 MB goes up in 64 MB parts through /api/upload/file/parts), and POST /api/upload/complete. The same limits as the website apply: up to 5 GB per build, 512 MB per file, 5,000 files. Pass the build folder or the build's .zip: the helper unpacks a zip on your machine and sends its files the same way. The result includes uploadId, testUrl and the static check report; fix a broken verdict and upload again. When you change a build you already uploaded, add --from <your game's slug or your last uploadId>: files this helper sent before and that haven't changed are copied instead of sent again, so a small change is quick even on a big game. A ROM mod (kind "patch") is its one patch file (.ips, .ups, .bps or .xdelta) and no index.html: pass the file itself to the helper and it is staged as a package with no page to check; a cosmetic's folder is staged with --package (by hand, POST /api/upload/start with package: true beside files). On an "Ideas and test builds only" connection (scope build) the helper works with upload_token's token and stages a private test build; upload_token's reply there gives the steps. Then call this tool (or POST the same fields to https://yougame.co/api/agent/update) with the game's slug (from my_games or its URL), the new uploadId, the kind of update, and patch notes. kind "major" (2.0) is for a big change: everyone who saved or liked the game is notified with the notes, and the home feed features the game for a week. kind "minor" (1.1) is for fixes and small changes: listed in the version history, nobody is pinged. Default to minor unless the creator says the update is big. Optional platform switches the listing between web and desktop_app; native-only games upload their build from Manage → Desktop builds.

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": {
      "slug": "<slug>",
      "uploadId": "<uploadId>"
    },
    "name": "update_game"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNomajor (big change, players are notified) or minor (fixes, silent). Default minor.
slugYesThe game's slug: the last part of its URL, https://yougame.co/g/<slug>.
notesNoPatch notes, up to 2000 characters: what changed, for players. Shown on the game page and, for a major update, in the notification.
videoNoOptional: a new preview video, as an MP4/WebM path inside the new build (under 100 MB). Omit to keep the current one.
licenceNoCreator-owned listing licence: all-rights-reserved, MIT, Apache-2.0, CC-BY-4.0 (art and sound), or custom. Omit or use null for not stated. Custom needs an https link in licence_url. Community open-source listings keep YouGame's AGPL licence. Unreal Engine games can't use GPL-family or CC BY-SA licences.
platformNoOmit to keep the current setting. web: plays in the browser. desktop_app: native build only; upload from Manage → Desktop builds. Forces mobile false. Never ship a web page telling players to download the app.
uploadIdYesThe new build, from the upload reply (32 hex characters).
upstreamNoFor a remix whose build was merged by hand after sync_remix reported conflicts: the original's build id the merge took (origin.upload_id in that reply), recorded as the remix's new base.
base_gameNoOptional replacement rom_patch for this release, including variants. Uses the listing's stored accepted dumps; edit other base-game metadata separately.
thumbnailNoOptional: a new thumbnail, as a path inside the new build (16:9 PNG/JPG/WebP/GIF under 8 MB). Omit to keep the current one.
licence_urlNoAn https link to the creator's licence text; required for custom, optional for other licences. No whitespace or control characters. Omit to keep it on updates; null clears it.
screenshotsNoOptional: new screenshots, as paths inside the new build. Omit to keep the current ones.
match_replaysNoEnable or disable browser match replays; omit to follow yougame.json or retain the listing setting.
whole_game_lobbyNotrue when online play is a single lobby that starts the whole game together; false when players pick among several lobby or mode types inside the game (no Play together button on its page). Omit if unsure; null clears the setting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • removedInput schema / properties / api_key
      Removed value: -{
      -  "description": "Only when the key could not be set as the Authorization header of the MCP connection: the creator's API key (yg_…). Prefer the header (or the YOUGAME_API_KEY environment variable): a key passed here ends up in the agent's transcript and tool logs.",
      -  "type": "string"
      -}
    • addedInput schema / properties / base_game
      Added value: +{
      +  "description": "Optional replacement rom_patch for this release, including variants. Uses the listing's stored accepted dumps; edit other base-game metadata separately.",
      +  "properties": {
      +    "rom_patch": {
      +      "description": "A cartridge ROM hack's default patch and optional patches for specific accepted dumps. Upload every named file. The default applies when no variant matches the player's SHA-1.",
      +      "properties": {
      +        "file": {
      +          "description": "Default patch's path inside the upload.",
      +          "type": "string"
      +        },
      +        "format": {
      +          "description": "Inferred from the file extension when omitted.",
      +          "enum": [
      +            "ips",
      +            "bps",
      +            "ups",
      +            "xdelta"
      +          ],
      +          "type": "string"
      +        },
      +        "variants": {
      +          "items": {
      +            "properties": {
      +              "file": {
      +                "description": "This copy's patch path inside the upload.",
      +                "type": "string"
      +              },
      +              "format": {
      +                "description": "Inferred from the file extension when omitted.",
      +                "enum": [
      +                  "ips",
      +                  "bps",
      +                  "ups",
      +                  "xdelta"
      +                ],
      +                "type": "string"
      +              },
      +              "sha1": {
      +                "description": "One of accepted's SHA-1s; each hash appears at most once.",
      +                "pattern": "^[0-9a-f]{40}$",
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "sha1",
      +              "file"
      +            ],
      +            "type": "object"
      +          },
      +          "maxItems": 8,
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "file"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "rom_patch"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / licence
      Added value: +{
      +  "description": "Creator-owned listing licence: all-rights-reserved, MIT, Apache-2.0, CC-BY-4.0 (art and sound), or custom. Omit or use null for not stated. Custom needs an https link in licence_url. Community open-source listings keep YouGame's AGPL licence. Unreal Engine games can't use GPL-family or CC BY-SA licences.",
      +  "enum": [
      +    null,
      +    "all-rights-reserved",
      +    "MIT",
      +    "Apache-2.0",
      +    "CC-BY-4.0",
      +    "custom"
      +  ],
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / licence_url
      Added value: +{
      +  "description": "An https link to the creator's licence text; required for custom, optional for other licences. No whitespace or control characters. Omit to keep it on updates; null clears it.",
      +  "maxLength": 500,
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / match_replays
      Added value: +{
      +  "description": "Enable or disable browser match replays; omit to follow yougame.json or retain the listing setting.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / platform
      Added value: +{
      +  "description": "Omit to keep the current setting. web: plays in the browser. desktop_app: native build only; upload from Manage → Desktop builds. Forces mobile false. Never ship a web page telling players to download the app.",
      +  "enum": [
      +    "web",
      +    "desktop_app"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / upstream
      Added value: +{
      +  "description": "For a remix whose build was merged by hand after sync_remix reported conflicts: the original's build id the merge took (origin.upload_id in that reply), recorded as the remix's new base.",
      +  "type": "string"
      +}
    • addedInput schema / properties / video
      Added value: +{
      +  "description": "Optional: a new preview video, as an MP4/WebM path inside the new build (under 100 MB). Omit to keep the current one.",
      +  "type": "string"
      +}
    • addedInput schema / properties / whole_game_lobby
      Added value: +{
      +  "description": "true when online play is a single lobby that starts the whole game together; false when players pick among several lobby or mode types inside the game (no Play together button on its page). Omit if unsure; null clears the setting.",
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
  2. Added

TDQS

A3.7/5.0
Behavior5/5

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

Beyond the annotations (non-destructive, idempotent), the description discloses authentication requirements, the staging helper workflow, upload limits (5 GB per build, 512 MB per file, 5,000 files), and the consequences of major versus minor updates (notifications and a week of home-feed featuring versus silent version-history listing). It also confirms that scores and comments are kept, which is meaningful behavioral context.

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

Conciseness2/5

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

The description is very long and buries the core purpose after an initial sentence about authentication. It includes extensive staging-helper instructions that read like procedural documentation rather than a tool definition, making it hard to scan for the key action and parameters.

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

Completeness4/5

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

For a complex tool with 14 parameters and nested objects, the description covers the main update flow, authentication, staging, limits, update-kind effects, platform behavior, and ROM mod handling. It also notes that the result includes uploadId, testUrl, and a static check report. Some parameter details are left to the fully covered schema, which is acceptable.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all 14 parameters. The description adds some meaning for kind (major notifies everyone and features the game for a week; minor is silent) and platform (forces mobile false, never ship a web page telling players to download the app). Many parameters such as upstream, base_game, thumbnail, screenshots, licence, and match_replays are left entirely to the schema.

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

Purpose4/5

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

The description states a specific verb and resource: 'Ships a new build of a game the creator already published, as its next version: same link, same origin, scores and comments kept.' This clearly distinguishes updating an existing game from publishing a new one. It does not explicitly differentiate this tool from the sibling add_version, leaving some ambiguity.

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

Usage Guidelines3/5

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

It gives parameter-level guidance ('Default to minor unless the creator says the update is big') and an exclusion for native-only games ('upload their build from Manage → Desktop builds'). However, it does not state when to use update_game versus alternatives like add_version or publish_game, so tool selection is only implied.

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