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 (from get_referral_program or get_sandbox_traffic) spends that $3 traffic bonus without a social post and without using the separate share allowance. Reuse the same bonusId and applicationId after an uncertain answer. Poll the returned run id; 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–3 of them (different public HTTPS links from any platform) — never invent one. Each accepted link adds one boost unit to the campaign, up to three. 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 cabinet. Repeatedly submitting already accepted links reuses the same grant without changing its budget or dates. Add the remaining links later (up to three 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). A stale PENDING run is requeued with the same id and saved links.

Input Schema

TableJSON 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–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.
`applicationId`	Yes	Application (game) id, as returned by list_applications

Schema Changelog

Changes observed during successful MCP inspections.

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?

Beyond the annotations (destructiveHint=true, no idempotency), the description discloses rich non-obvious behavior: the $3 bonus is spent and reserved, a timeout is not permission to spend another bonus, uncertain DSP outcomes keep their reservation, requeueing reuses the same bonusId, and campaign budget/dates are extended on link additions. This greatly extends what annotations alone convey, with no contradictions.

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 description is very long and contains repetition ('extend it to at least three days from submission' appears twice, and 'up to three' claims recur). While the density is largely warranted for a money-spending tool with fail-safe rules, tighter editing would improve scannability without losing content.

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 high-complexity spending tool with no output schema, the description is remarkably complete: it covers preconditions, the PENDING → FAILED polling lifecycle with failureReason, specific error reasons (SHARE_REQUIRED, INVALID_POST_URL, PAYMENT_REQUIRED, RUN_IN_PROGRESS), and the paid-traffic fallback path. Nothing an agent needs to invoke it 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 schema already documents all three parameters heavily. The description nevertheless adds value beyond the schema: the 'exactly one of bonusId/postUrls' mutual-exclusion rule, the one-campaign-per-game / three-games-per-org cap, and the linkage between adding links and increasing the same campaign's budget. Slight redundancy with schema text but still additive.

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 first sentence 'Start an ad campaign that sends players to the sandbox page' names a specific verb, resource, and target, and the rest distinguishes the two traffic sources (referral bonus vs. share links). It is clearly separable from siblings like get_sandbox_traffic (status) and get_sandbox_share (post/links).

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?

The description explicitly states when to use each parameter path (bonusId from get_referral_program/get_sandbox_traffic vs. postUrls after the developer publishes), names get_sandbox_traffic for polling, and gives hard preconditions ('Needs covers in the published revision and the Bridge SDK', 'Ask the developer first'). Alternatives and exclusions are spelled out, not implied.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?