Skip to main content
Glama

Creatives: estimate an order

creative_estimate
Read-only

Price a creative order BEFORE placing it, from the same inputs creative_order takes: credits with a breakdown (images × quality + AI copy), the euro equivalent, whether the cabinet can afford it and whether it can be placed (the 16-image cap). Nothing is created or charged. Tell the person the price («N креативів = X кредитів ≈ €Y»). Read-only.

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": "creative_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNo
taskNoOptional hint for the model router.
briefYesWhat to advertise: product / service, offer, for whom.
eventNoFacts of a course / webinar / seminar / conference, printed EXACTLY as given (never invented): the event_poster layout sets them as the picture, other layouts get "date · time · place" in the offer line.
textsNo"auto" (default) = AI writes headline / CTA / caption (+20 credits once); or the exact texts to put on the banner (no copy charge).
presetNoA ready niche task (courses, consulting, trainings & events — see creative_options.presets): fills goal, channel, formats, layouts, styles and variants you leave out, adds the niche copy rules and a real-photo direction (unretouched expert, real hall). Some need facts: webinar / cohort_enrolment → event.date; seminar_invite → event.date + event.place; early_bird → event.date + event.early_price; client_case → big_number.
stylesNoStyle slugs from creative_style_list (cycled over variants), or "random12" for different random styles.
channelNoe.g. instagram_post, facebook, linkedin, tiktok, pinterest, google.
formatsNoFormats (≤4) — keys or aspect ratios from creative_options. Default ["square"].
layoutsNoBanner layout per variant (cycled). "auto" (default) picks a DIFFERENT layout for each variant to fit its style and the task: full_bleed (photo edge to edge, headline on its calm zone, no panel), editorial_split (magazine page, serif), color_block (flat bold colour + round photo), swiss_grid (grid, facts in columns), minimal_object (one object, a lot of air), big_typography (words only, no image), collage (the subject cut out of the photo over huge capitals + a round offer sticker), big_number (ONE real number from the brief as the picture, no image; needs big_number or a number in the brief), event_poster (the event's date huge + time, place, speaker, price, seats; no image; needs event.date or event.place). Layouts without an image cost 5 credits per creative at any quality. See creative_options.layouts.
qualityNodraft = 5 credits per image (default), final = 20.
audienceNo
languageNouk (default), en, de, …
variantsNoDefault 4.
big_numberNoThe number for the big_number layout exactly as the client states it, with its unit: "24", "−30%", "1 200 ₴", "15+". Never invent one. Without it the copy model takes a number written in the brief; with no number at all the auto-pick never chooses big_number.
referencesNoreference_id values from creative_reference_upload.
brand_kit_idNoA brand kit of THIS cabinet (brand_kit_list).
big_number_labelNo≤ 4 words printed above the number ("годин доставки").
big_number_sourceNoOptional source footnote under the number ("за даними CRM, 2025").

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?

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds substantive behavior: it returns a credit breakdown (images × quality + AI copy), euro equivalent, cabinet affordability, and placement feasibility against a 16-image cap. It also specifies a user-facing output format.

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-loaded with the core purpose, followed by concrete outputs and a usage constraint. Every sentence earns its place; 'Read-only' reinforces rather than pads.

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 read-only estimation tool with 19 parameters, nested event object, and no output schema, the description explains the key return values (cost breakdown, euro, affordability, placement cap) and reassures that nothing is created or charged. The schema carries the parameter-level detail.

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 description coverage is 89%, so the schema already explains nearly all parameters in detail. The description adds only broad hints—pricing depends on image quality and AI copy—without extending meaning for individual parameters beyond 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?

States a specific verb ('Price') and resource ('a creative order'), and immediately distinguishes itself from sibling creative_order by scoping to 'BEFORE placing it' and 'Nothing is created or charged'.

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?

Explicitly says to use this before placing an order and that it takes the same inputs as creative_order, routing the agent between estimating and creating. The no-charge/no-creation constraint clarifies when this tool is appropriate.

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