Skip to main content
Glama

Prepare content from a brief

playground_content_prepare
Read-only

The easiest way to start making content. Give a short brief and one entry per output you need; intendedUse is optional. You write each image or video prompt yourself: look at the reference image, describe the product (type, colour, material, details that must not change) and the shot (for example hero, lifestyle, detail, or a short motion plan), following the model prompt guide. If a prompt is missing, Berrys returns prompts_required with the reference preview and the guide instead of a quote; write the prompts and call again. Berrys then returns an exact, free credit quote; it does not create nodes or spend credits. For a new creative task, create a fresh project first with playground_project_create; for a follow-up, reuse its projectId. Import any uploaded or linked image to that project first and pass its image node ID as a reference. Audio needs the exact spoken words or lyrics. Review the returned prompts, references, defaults and price with the user; the returned mediaGenerateRequest is the exact input for playground_media_generate with quoteId and a new idempotencyKey when they want to proceed.

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": {
      "projectId": "<projectId>",
      "brief": "<brief>",
      "deliverables": "<deliverables>"
    },
    "name": "playground_content_prepare"
  }
}

Input Schema

NameRequiredDescriptionDefault
briefYesUser’s creative goal, product context and requirements for the deliverables.
localeNoLanguage or locale to use for the deliverable text, such as en or id-ID. Language tag such as en, id-ID, th-TH, or vi-VN.
brandIdNoAn explicitly selected brand owned by the connected account. Its saved rules are included in the quoted image/video prompts.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
intendedUseNoWhere the content will be used, for example a product listing, social post or ad. Omit when the user has no specific placement.General creative use
deliverablesYes

Output Schema

NameRequiredDescriptionDefault
nextNoSuggested next action; it does not authorize spending.
brandNo
briefNo
itemsNo
localeNo
reviewNo
statusYes
balanceNo
quoteIdNo
revisionNo
canvasUrlNo
expiresAtNoSerialized ISO timestamp.
projectIdNo
assumptionsNo
intendedUseNo
projectNameNo
promptGuidesNo
totalCreditsNo
validitySecondsNo
inputFingerprintNo
itemPromptGuidesNo
sufficientCreditsNo
mediaGenerateRequestNo
estimatedBalanceAfterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnlyHint=true / destructiveHint=false annotations, it discloses the key behavior: the call is free, produces a quote only, and creates no nodes or credits. It also documents the non-obvious failure path — a missing prompt yields prompts_required with the reference preview and guide instead of a quote — plus what the user should review before proceeding. Nothing here contradicts the annotations.

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?

Purpose and the free-quote guarantee are front-loaded, and each paragraph maps to a real step (write prompts, quote, prerequisites, downstream handoff). It is dense and long with some packed run-on sentences and slight repetition of the prompts_required condition, but for a 6-parameter, 20-deliverable, multi-step workflow the length is largely earned.

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?

Given the tool's complexity — nested deliverables array, reference node IDs, model constraints, and a quote-then-generate workflow — the description covers prerequisites, prompt authoring requirements, the prompts_required fallback, and the handoff to generation. An output schema exists, yet the description still usefully previews what is returned (prompts, references, defaults, price), so nothing an agent needs to call 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?

With schema coverage at 83% the baseline is 3, and the description adds real meaning on top: intendedUse is optional, deliverables are one entry per output, prompts must be written by the agent from the reference image following the model prompt guide, and audio requires the exact spoken words or lyrics. It doesn't add much on locale, brandId, or count/aspectRatio beyond what the schema already says.

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 concrete verb and resource — take a brief plus one deliverable entry per output and return an exact, free credit quote — and explicitly separates that from what siblings do ('it does not create nodes or spend credits', and mediaGenerateRequest feeds playground_media_generate). An agent can tell this is the quote/prepare step rather than the generation step 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 when-to-use and sequencing rules: create a fresh project with playground_project_create for a new task, reuse projectId for a follow-up, import uploaded or linked images first and pass the image node ID as a reference. It also names the downstream alternative and the exact handoff condition (proceed via playground_media_generate with quoteId and a new idempotencyKey).

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.