Skip to main content
Glama

Create a design

create_design

Create a design (a full-screen slide for a screen, such as a menu, an announcement or an event poster) from a description. It picks a fitting template, fills in the text and adds stock photos where the template has them; no images are generated with AI. The design is saved in the team's files and can be shown on a screen or used in a scene. Each design uses the account's AI budget, with at most 20 designs per hour.

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

Input Schema

NameRequiredDescriptionDefault
nameNoName of the design in Screenbird. Optional.
briefYesWhat the design must show, in the user's words, with all texts, prices, times and names to put on it. For a list whose entries are not known yet, give the number of entries as digits ("a menu with 10 dishes"); never placeholders or made-up names: the designer adds placeholders itself.
languageNoTwo-letter language code of the texts on the design (en, nl, de, ...).
orientationNoScreen orientation. Default landscape.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / brief / description
      Previous value: -"What the design must show, in the user's words, with all texts, prices, times and names to put on it."New value: +"What the design must show, in the user's words, with all texts, prices, times and names to put on it. For a list whose entries are not known yet, give the number of entries as digits (\"a menu with 10 dishes\"); never placeholders or made-up names: the designer adds placeholders itself."
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well past the annotations (readOnly=false, openWorld=true, destructive=false) by disclosing the generation pipeline (picks a template, fills text, adds stock photos), the important negative constraint 'no images are generated with AI', where output lands ('saved in the team's files'), and the cost/quota profile (AI budget, 20 designs per hour). These are exactly the operational facts an agent needs before invoking a generative, budget-consuming write.

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 with what is created, followed by mechanics, storage destination, and limits in a logical order. Three sentences of dense but non-redundant content; only minor trimming (e.g. the parenthetical example list) would be possible.

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 four-parameter generative write tool with no output schema, the description covers mechanism, side effects, storage location, cost, and rate limit. The main omission is what is returned (design identifier, URL, or preview) and whether the call is synchronous, which would matter for chaining into push_content or a scene.

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%, so every parameter is already documented in the schema, and the description adds no format or syntax detail beyond it. It reinforces that generation is driven by the brief, but that is already conveyed by the schema's brief description; 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 (Create) and resource (a design), then parenthetically defines the resource for anyone unfamiliar: 'a full-screen slide for a screen, such as a menu, an announcement or an event poster'. The 'from a description' clause makes the generation mechanism unambiguous, which no sibling tool shares.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: 'can be shown on a screen or used in a scene' sketches the downstream workflow but never says when to pick this over searching for existing content (search_content) or pushing content (push_content). No explicit when-not-to-use or prerequisite steps are given.

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