Skip to main content
Glama

AI Promo Design

by com.aipromodesign
OverviewDiscussionsAdmin

Design artwork for an item

design_item

Make a print-ready design from a short description, for one item in one color. Returns a watermarked preview of the design on the item, a design_id for revise_design and open_in_studio, and how many free designs are left. Describe the ARTWORK only ("a snarling wolf head, two colors"), not the garment: the garment is chosen with item and color. Each call makes one design and spends one from the allowance (10 as a visitor, then 25 a day on an aipromodesign.com account). Pass back the visitor value from the previous answer so the allowance follows the customer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemNoItem key or the word a customer would use (tee, hoodie, mug, tote, cap, polo, long sleeve, crewneck, performance tee, women's tee, youth hoodie, notebook, tumbler). Use list_items for the full set. Defaults to the adult tee.
briefYesWhat the artwork shows, in the customer's words. The artwork alone - no shirt, no mug.
colorNoThe item's color by name (Navy, Black, White, Forest Green, Sport Gray, Red, Royal, Maroon...). Defaults to White.
surfaceNoWhich print area: front (default), back, left_sleeve, right_sleeve. The design is sized for it.
visitorNoThe visitor value from an earlier answer in this conversation, if there was one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the cost model (one design per call, 10 as a visitor, 25/day on an account), the return shape (watermarked preview, design_id, remaining free designs), and the stateful visitor handoff. The non-idempotent hint is confirmed by 'each call makes one design and spends one from the allowance'.

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?

Front-loads the core action, then the return values, then the usage constraint and cost/visitor rule. Every sentence carries operational information with no filler.

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?

Even without an output schema, the description names what comes back (preview, design_id, remaining allowance), states the consumption rule, and ties the tool to its siblings. Nothing an agent needs to invoke 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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning for `visitor` (why it must be echoed back to keep the allowance with the customer) and clarifies the brief/item/color division of responsibility beyond the schema's own wording.

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 ('Make a print-ready design... for one item in one color') and immediately scopes the input to artwork rather than garment. This clearly separates it from revise_design (which takes an existing design_id) and list_items.

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

Usage Guidelines4/5

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

Gives explicit guidance on what to pass ('Describe the ARTWORK only... the garment is chosen with `item` and `color`') and instructs passing back `visitor` so the allowance follows the customer. It implies but does not explicitly state when to prefer revise_design over a fresh design call.

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

All AI Promo Design toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources