Skip to main content
Glama

Create a Playground project

playground_project_create

Create a new, empty Playground project owned by the signed-in user. For a fresh generation request with no named, linked or conversation-established project, create one automatically with a concise name from the brief; do not ask for separate project-creation permission or inspect unrelated projects first. Reuse its ID for follow-up work on the same task. General questions do not need a project. Creation spends no credits; paid generation still requires a quote and user approval. Returns the project ID and canvasUrl.

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

Input Schema

NameRequiredDescriptionDefault
nameYesConcise project name describing the user’s creative task.

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
effectsNo
revisionYes
canvasUrlYes
projectIdYes
spendModeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Adds real context beyond the annotations: creation spends no credits, while paid generation still needs a quote and user approval. The annotations already declare non-destructive, non-read-only, non-open-world behavior, so the description's remaining gap is that it never warns that repeat calls create separate projects (consistent with idempotentHint=false).

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 imperative sentence followed by tightly packed operating rules; all sentences carry decisions the agent must make. The closing "Returns the project ID and canvasUrl" is partly redundant with the existing output schema.

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 single-parameter creation tool with full schema coverage, annotations, and an output schema, this covers ownership, cost, and permission posture well. Duplicating return values is unnecessary, and the consequence of calling it twice is left to the idempotency annotation.

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 coverage is 100% and the name parameter already carries a description close to "concise name from the brief." The description's naming guidance is directionally useful but largely restates what the schema says, so 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?

States a specific verb and resource ("Create a new, empty Playground project") plus ownership scope ("owned by the signed-in user"). The word "empty" and the auto-creation guidance make it unambiguous versus canvas or generation 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 ("fresh generation request with no named, linked or conversation-established project"), when-not-to ("General questions do not need a project"), and even removes a common hesitation by saying not to ask for separate permission or inspect unrelated projects first.

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.