Playgama MCP - Publish & Manage HTML5 Games

Bring traffic to the sandbox

start_sandbox_traffic

Destructive

Start an ad campaign that sends players to the sandbox page. Send exactly one of bonusId or postUrls. A referral bonusId (get_referral_program) needs no social post; a timeout is not permission to spend another bonus. The separate share traffic bonus: first help the developer post the game (get_sandbox_share has the post and links), then ask the developer to paste the links of their published posts and pass 1–2 of them (different public HTTPS links from any platform) — never invent one. Each accepted link adds one boost unit to the campaign, up to two. One campaign per game, three games per organization for its lifetime; earlier free runs without sharing do not count. No dollar amount. Ask the developer first. Needs covers in the published revision and the Bridge SDK. Answers the PENDING run; poll get_sandbox_traffic for the returned run.id until it leaves PENDING — FAILED carries failureReason. Only a confirmed safe failure makes a referral bonus retryable; an uncertain DSP outcome keeps its reservation. A refusal carries the reason get_sandbox_traffic shows, or SHARE_REQUIRED / INVALID_POST_URL for missing or invalid links; PAYMENT_REQUIRED: paid traffic is in the console. Repeatedly submitting already accepted links reuses the same grant without changing its budget or dates. Add the remaining link later (up to two total) to increase the same campaign budget and extend it to at least three days from submission, including after it has finished. New links wait while a launch/update is PENDING (RUN_IN_PROGRESS).

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": {
      "applicationId": "<applicationId>"
    },
    "name": "start_sandbox_traffic"
  }
}

Input Schema

Name	Required	Description
`bonusId`	No	Referral bonus id returned by get_referral_program or get_sandbox_traffic. Send bonusId OR postUrls, never both. A referral bonus requires no social post. Reuse the same bonusId and applicationId after a timeout; never choose a new bonus to retry an unknown outcome.
`postUrls`	No	1–2 different public HTTPS post URLs from any platform. The developer must publish the posts first. Each accepted link adds one boost unit to the same campaign, up to two. Send new links now or later, up to two total per game. Already accepted links are not credited again. Each addition extends the same campaign to at least three days from submission.
`applicationId`	Yes	Game id from list_applications

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026

changedInput schema / properties / applicationId / description

Previous value: -"Application (game) id, as returned by list_applications"New value: +"Game id from list_applications"

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / postUrls / description

Previous value: -"1–3 different public HTTPS post URLs from any platform. The developer must publish the posts first. Each accepted link adds one boost unit to the same campaign, up to three. Send new links now or later, up to three total per game. Already accepted links are not credited again. Each addition extends the same campaign to at least three days from submission."New value: +"1–2 different public HTTPS post URLs from any platform. The developer must publish the posts first. Each accepted link adds one boost unit to the same campaign, up to two. Send new links now or later, up to two total per game. Already accepted links are not credited again. Each addition extends the same campaign to at least three days from submission."

changedInput schema / properties / postUrls / maxItems
```
Previous value: -3New value: +2
```

Changed2 schema fields changedSep 20, 2026

addedInput schema / properties / bonusId

Added value: +{
+  "description": "Referral bonus id returned by get_referral_program or get_sandbox_traffic. Send bonusId OR postUrls, never both. A referral bonus requires no social post. Reuse the same bonusId and applicationId after a timeout; never choose a new bonus to retry an unknown outcome.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "applicationId",
-  "postUrls"
-]New value: +[
+  "applicationId"
+]

Changed1 schema field changedSep 17, 2026

changedInput schema / properties / postUrls / description

Previous value: -"1–3 different public HTTPS post URLs from any platform. The developer must publish the posts first. Each accepted link adds one boost unit to the same campaign, up to three. Submit all available post links together; the once-per-game bonus cannot be increased by a repeat request."New value: +"1–3 different public HTTPS post URLs from any platform. The developer must publish the posts first. Each accepted link adds one boost unit to the same campaign, up to three. Send new links now or later, up to three total per game. Already accepted links are not credited again. Each addition extends the same campaign to at least three days from submission."

Changed1 schema field changedSep 16, 2026

changedInput schema / properties / postUrls / description

Previous value: -"1–3 different public HTTPS post URLs from any platform. The developer must publish the post first. One post is enough; extra posts do not increase the boost."New value: +"1–3 different public HTTPS post URLs from any platform. The developer must publish the posts first. Each accepted link adds one boost unit to the same campaign, up to three. Submit all available post links together; the once-per-game bonus cannot be increased by a repeat request."

Changed1 schema field changedSep 16, 2026

changedInput schema / properties / postUrls / description

Previous value: -"1–3 different public post URLs from X, LinkedIn, Threads or Facebook. The developer must publish the post first. One post is enough; extra posts do not increase the boost."New value: +"1–3 different public HTTPS post URLs from any platform. The developer must publish the post first. One post is enough; extra posts do not increase the boost."

Changed2 schema fields changedSep 16, 2026

addedInput schema / properties / postUrls

Added value: +{
+  "description": "1–3 different public post URLs from X, LinkedIn, Threads or Facebook. The developer must publish the post first. One post is enough; extra posts do not increase the boost.",
+  "items": {
+    "maxLength": 2048,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 3,
+  "minItems": 1,
+  "type": "array"
+}

changedInput schema / required

Previous value: -[
-  "applicationId"
-]New value: +[
+  "applicationId",
+  "postUrls"
+]

AddedSep 14, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Far beyond the annotations, it discloses lifetime quotas (one campaign per game, three per organization), that no dollar amount is charged, that an uncertain DSP outcome keeps its reservation and only a confirmed safe failure makes a bonus retryable, and that resubmitting accepted links reuses the same grant without changing budget or dates. It also explains post-submission state (PENDING/FAILED with failureReason) and how to poll.

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

Conciseness3/5

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

The purpose is front-loaded, but the body is a dense run-on of clauses and fragments ('No dollar amount.', 'Earlier free runs without sharing do not count.') that mixes prerequisites, quotas, retry policy and error codes without ordering. Nearly every sentence carries information, but the lack of structure makes it slow to parse for an agent deciding whether to call it.

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?

For a destructive, open-world, non-idempotent mutation with no output schema, it covers prerequisites, side effects on campaign budget and duration, the pending-run handoff to get_sandbox_traffic, and the failure vocabulary. An agent has enough to call it correctly and to interpret the result.

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, but the description adds real decision-level meaning: bonusId and postUrls are mutually exclusive, links must be different public HTTPS URLs the developer actually published, never invented, and 1–2 of them each add one boost unit up to two. Most of this is duplicated in the per-parameter descriptions rather than adding new semantics.

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 opening sentence states a specific verb and resource: 'Start an ad campaign that sends players to the sandbox page.' It also names the sibling tools that surround it (get_referral_program for the bonus, get_sandbox_share for the post, get_sandbox_traffic for polling), so an agent can place it precisely without opening any schema.

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?

It gives explicit routing rules: 'Send exactly one of bonusId or postUrls,' explains that a referral bonus needs no post while share traffic requires the developer to publish first, and states prerequisites (ask the developer first, covers in the published revision, Bridge SDK). It also names the exclusions and their error signals (SHARE_REQUIRED, INVALID_POST_URL, PAYMENT_REQUIRED, RUN_IN_PROGRESS).

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

All Playgama MCP - Publish & Manage HTML5 Games tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?