Skip to main content
Glama

Heista

by co.heista

Call Creative Worlds

call_creative_worlds

Heista's creative direction engine — same engine the Creative Director specialist runs internally, exposed over MCP. ONE-SHOT: give a brief, get N finished creative outputs. For back-and-forth refinement, or output shapes the medium enum below does not cover, use chat_with_creative_worlds instead.

OUTPUT SHAPE switches on the medium arg: • omitted → N territory cards (default exploration). Each card sits on different psychology / craft / feel / world axis coordinates so the set spans the creative space rather than orbiting one insight. Card has: name, campaign line, 5-8 sentence pitch, one-sentence strategic bet, resolved axis state names, creative-director rationale. • tvc → N TVC scripts (15-90s — hook, arc, resolve, sound design, end line). • billboard / ooh / print → N out-of-home concepts (visual concept + line + placement rationale). • social → N social-video concepts (hook + format type + middle beat + payoff, optimised for Reels / TikTok / Shorts). • activation / experiential → N activation concepts (space design + user journey + peak moment + takeaway artifact). • audio → N sonic / radio concepts (sonic scene + voice + audio arc). • campaign → N full campaign platforms (insight → big idea → strategy → visual world → production roadmap).

The engine can also produce manifesto / copy, naming, packaging, PR stunts, content series, brand positioning, partnerships — these output shapes are NOT in the medium enum, so use chat_with_creative_worlds when the user wants one of those.

USE WHEN: user says "give me ideas / options / directions / territories", "what angles work for...", "show me three / five ways to...", "write a TVC for...", "draft billboard concepts for...", "I need fresh thinking on...". DO NOT USE to refine one existing direction (use chat tool), to critique work, for OKRs / internal docs / strategy decks, or anything outside advertising creative direction.

INPUTS: brief (the creative problem, free text), count (2-6 concepts), optional brand_id (from list_brands or any create_powersource_* — when provided the engine grounds output in the brand's buyer tensions, voice, and selling points), optional medium (above), optional lens_hint (apply a playbook or signature move as a creative constraint), idempotency_key (safely retryable for 5 minutes).

Returns the finished creative output as narrative text PLUS a structured array of resolved axis coordinates for programmatic use. Metered — typically 3-15 credits per call depending on count and brand context size. Charged after success on actual token usage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
briefYesThe creative brief — what you want territory directions for. One sentence or short paragraph. Example: "Hero campaign for a sparkling water brand launching in Australia, positioned against soft drink as the everyday adult alternative".
countYesHow many distinct creative territories to generate. Each will sit on different axis coordinates from the others — different psychology, different feel, different world. 2-6.
mediumNoOptional medium — switches the output shape. Omit → territory cards (default exploration). `tvc` → TVC scripts (hook + arc + resolve + sound + end line). `billboard` / `ooh` / `print` → out-of-home concepts (visual + line + placement). `social` → Reels / TikTok / Shorts concepts. `activation` / `experiential` → activation concepts (space + journey + peak moment + takeaway). `audio` → sonic / radio concepts. `campaign` → full campaign platforms (insight → big idea → strategy → visual world → production roadmap). See the tool description for the full per-shape spec.
brand_idNoOptional Heista brand id (a.k.a. brief id) to ground the territories in. Get from list_brands or any create_powersource_* call. When provided, the engine pulls the brand intelligence (buyer tensions, voice, selling points) and uses it as the entry point into psychology axes. Omit for an unbranded creative exploration.
lens_hintNoOptional creative lens to constrain the direction. Applied throughout the ideation as a creative constraint. Use when an agent has already picked a playbook or signature move and wants territories under that lens.
idempotency_keyNoOptional unique key to make this call safely retryable. If the same key + org repeats within 5 minutes, the original result is returned without re-charging.

TDQS

A4.9/5.0
Behavior5/5

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

Goes beyond annotations: describes it as a one-shot engine mirroring the internal Creative Director specialist, details output shape switching via medium, notes metered credit usage (3-15) and post-success charging, and mentions structured array for programmatic use. No contradictions with annotations.

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?

Well-structured with clear sections and bullet-like formatting, but somewhat lengthy due to exhaustive detail. Front-loads purpose and key distinction, though could be slightly tightened without losing clarity.

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?

Covers all 6 parameters, nested object, output shapes per medium, usage guidance, billing, and integration points. Without output schema, the description fully compensates by detailing return format for each medium.

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

Parameters5/5

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

100% schema coverage already; description adds extensive context: brief examples, count range rationale, full medium enum breakdown with output shape specs, brand_id integration with other tools, lens_hint nested structure, and idempotency_key safety guarantee.

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 explicitly states the tool is Heista's creative direction engine, providing one-shot generation of N finished creative outputs from a brief. It clearly distinguishes from the sibling chat_with_creative_worlds for refinement, and lists concrete use cases.

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?

Provides explicit 'USE WHEN' examples (e.g., 'give me ideas/options/directions', 'write a TVC for...') and clear 'DO NOT USE' exclusions (refinement, critique, non-advertising tasks). Also references the alternative sibling tool for specific scenarios.

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

All Heista toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation4/5

Despite the high tool count, most tools have distinct purposes with thorough descriptions that specify when to use each. Some overlap exists among creative direction tools (call_creative_worlds vs chat_with_creative_worlds), but the descriptions clarify usage patterns.

Naming Consistency3/5

Naming conventions are inconsistent overall: some follow verb_noun (create_powersource_url, decode_ad), others use noun_verb or compound names (adformula_intelligence, fleet_analytics_overview). However, subgroups like dispatch_* and list_*_presets maintain internal consistency.

Tool Count2/5

112 tools is far beyond the typical 3-15 range for well-scoped servers. While the server covers a broad domain, the sheer number likely overwhelms agents and suggests insufficient consolidation of related operations.

Completeness4/5

The tool set covers core creative intelligence workflows: brand analysis, ad decoding, script generation, creative direction, and research. Minor gaps exist (e.g., no social media publishing tools), but the main use cases are well-supported.

Resources