Skip to main content
Glama

generate_creative_brief

Read-onlyIdempotent

Build an evidence-grounded creative brief from source identity, actual routes, and explicit audience and goal inputs to guide motion projects.

Instructions

Build an evidence-grounded creative brief from source identity, actual routes and explicit audience/goal.

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": {
      "project": "<project>",
      "audience": "<audience>",
      "goal": "<goal>"
    },
    "name": "generate_creative_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYes
projectYes
audienceYes
languageNoEnglish
directionNominimal

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds the meaningful hint that output is "evidence-grounded" from prior discovery, but never states whether identity/route detection must run first or what happens when that evidence is absent.

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?

A single front-loaded sentence with no filler, and the core action leads. Density comes at a cost though: "source identity" and "actual routes" are compressed terms that are never unpacked.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values needn't be explained, but with five parameters at 0% schema coverage and two defaulted enums, the definition leaves the agent guessing about input formats and how direction/language affect the brief. The implied dependency on prior detection tools is also unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden, yet it only clarifies audience and goal ("explicit"). The three remaining parameters are untouched: project is undescribed (path? URL? name?), and direction and language are enums with defaults whose meaning and effect are never explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("Build an evidence-grounded creative brief") and qualifies the inputs it draws from. It distinguishes itself from analysis or rendering tools by framing the output as a brief, but the phrases "source identity" and "actual routes" are undefined jargon that only loosely connect to siblings like detect_brand_identity or discover_routes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no prerequisites stated, and no named alternatives (e.g., generate_storyboard or create_scene_plan for downstream steps). The agent must infer that this is an early planning step from the word "brief" alone.

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