Skip to main content
Glama

Create brief

create_brief

A Brief is the brand guidance and files Rainbrand selects for the work you're doing. Use one Brief for closely related work that shares the same goal, audience, creative direction, and source material. Request a new Brief when any of those change meaningfully. Use get_brand for a general overview of the brand. Returns the brief_id and status immediately. Then call get_brief with the returned brief_id and wait: true, and inspect the completed guidance and assets before using them.

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": {
      "brand_session_id": "<brand_session_id>",
      "task": "<task>"
    },
    "name": "create_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesWhat you are about to make, in plain language. Include any context or instructions that would help select the right brand guidance and files.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.
idempotency_keyNoRetry key for recovering the original Brief request. Reuse the same key with identical input.
brand_session_idYesBrand session ID from list_brands for the brand to prepare the brief from.

Output Schema

NameRequiredDescriptionDefault
statusYesCurrent brief status.
brief_idYesBrief ID. Pass it as brief_id to get_brief.
message_for_assistantNoContext, explanations, or actionable guidance for the calling assistant. Hosts may display it, but it is not copy that must be shown to the user verbatim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Beyond the annotations, it discloses the async contract: the call returns brief_id and status immediately and results must be fetched via get_brief with wait: true, with an instruction to inspect guidance and assets before using them. What it does not cover is cost side effects (a related check_credits sibling hints at credit consumption) or failure/timeout handling, leaving a gap for a non-idempotent, open-world creation tool.

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?

Five short sentences, front-loaded with the concept definition, then reuse policy, sibling routing, and the follow-up call sequence. Every sentence carries operative information and none restates the tool name or annotations.

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 creation tool with four documented parameters and an output schema, the description supplies the missing pieces: what a Brief is, when to create a new one, and the two-step create-then-poll workflow. The remaining return-value details are covered by the output schema.

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 already 100%, so the baseline is 3; the description earns a bump by defining the scope conditions that should drive how the required `task` string is written and when a new task warrants a new Brief. It adds nothing for idempotency_key or llm_model, but those are adequately documented in the schema.

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 defines the resource concretely ("A Brief is the brand guidance and files Rainbrand selects for the work you're doing") and makes clear this tool requests a new one. It distinguishes itself from the closely named siblings by naming get_brief (for polling results) and get_brand (for a general brand overview).

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 an explicit reuse rule — one Brief for work sharing goal, audience, creative direction, and source material — and an explicit create-new rule when any of those change. It also routes the agent to get_brand when only a general overview is wanted, which is a genuine when-not condition.

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.

Resources