yagames-mcp

yagames-create-draft

Create a new game draft in the Yandex Games Console by submitting essential metadata: title, description, how to play, category, age rating, languages, orientation, and platforms.

Instructions

Create a new game draft in the Yandex Games Console. Requires YAGAMES_SESSION_COOKIE and YAGAMES_CSRF_TOKEN env vars

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": {
      "title": "<title>",
      "description": "<description>",
      "howToPlay": "<howToPlay>",
      "category": "<category>",
      "ageRating": "<ageRating>",
      "languages": "<languages>",
      "orientation": "<orientation>",
      "platforms": "<platforms>"
    },
    "name": "yagames-create-draft"
  }
}

Input Schema

Name	Required	Description
`seo`	No	SEO description (50-160 chars)
`tags`	No	Tags describing the game (max 20)
`title`	Yes	Game title (max 50 chars)
`category`	Yes	Genre categories (max 2)
`ageRating`	Yes	Age rating
`howToPlay`	Yes	How to play instructions (100-1000 chars)
`languages`	Yes	Languages the game supports (e.g. ["ru", "en"])
`platforms`	Yes	Supported platforms: desktop, mobile_ios, mobile_android
`cloudSaves`	No	Whether the game uses cloud saves via SDK
`description`	Yes	Full description (100-1000 chars)
`orientation`	Yes	Screen orientation
`developerComment`	No	Comment for moderation team (max 2048 chars)
`shortDescription`	No	Short description (max 70 chars)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 6, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses a meaningful operational prerequisite — the two required auth env vars (YAGAMES_SESSION_COOKIE, YAGAMES_CSRF_TOKEN) — which is genuinely useful. However, it does not describe side effects, rate limits, or expected response behavior for the mutation it performs.

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

Conciseness5/5

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

Two sentences with zero waste: the core purpose is front-loaded and the critical auth requirement immediately follows. Every sentence earns its place.

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 13-parameter create operation, the description covers the biggest hidden prerequisite (auth env vars) while all parameters are fully documented in the schema. The only gap is the absence of return-value/output information, which would help an agent track the created draft, but no output schema exists to offset this.

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 every parameter (title, category, ageRating, etc.) is already documented with constraints in the input schema. The tool description adds no parameter-level meaning beyond what the schema provides, so the baseline 3 applies.

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?

The description states a specific verb ('Create') and resource ('a new game draft in the Yandex Games Console'), making the tool's function immediately identifiable. The word 'new' also implies creation of a fresh draft, which distinguishes it from the yagames-update-draft sibling.

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?

Usage context is implied: 'Create a new game draft' signals this is for initial creation, contrasting with the update-draft sibling in the tool list. However, no explicit when-to-use guidance or exclusion statements are given; the description relies on inference.

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

Deploy Server