Skip to main content
Glama
Sign In

Clueso

by io.clueso
OverviewDiscussionsAdmin

Create clueprint

create_clueprint

Create a new clueprint (reusable video template). A clueprint is a structured file directory with design notes, composition rules, and screenshots that can be used to generate videos.

Use human-readable folder categories: design/ (colors, typography, backgrounds, animation), rules/ (composition, voiceover, editing), screenshots/ (rendered clip previews). See the "Creating Clueprints" section in the system instructions for the full structure.

If source_guide_ids are provided, guide data is extracted clip-by-clip into the clueprint (animations and images described, auto-element rules learned; can take minutes). Each non-empty decision list in the reply (animations_pending_mode, logo_animations, images_pending_mode, clips_pending_voiceover_policy, multi_split_summary, slide_count_strategy, the *_by_role groups, discovered_element_types_by_clip_type) is a choice to ask the user, then record with update_clueprint(decisions).

A clueprint is THE FORMAT (layouts, pacing, motion, transitions, voiceover style, music, captions, effects); a project built from it takes its colors, fonts and logos from that project's brand kit. brand_locked: true keeps the clueprint's own colors, fonts and logos for projects in this workspace (for a template made for one brand, e.g. a co-marketing piece).

Input Schema

NameRequiredDescriptionDefault
nameYesName of the clueprint
visibilityYes'workspace' shares it with your workspace; 'private' is stored as 'workspace'.
descriptionNoDescription of what this clueprint does
brand_lockedNotrue: projects in this workspace built from this clueprint keep its own colors, fonts and logos instead of their brand kit's. Default false (re-skinned to the project's kit).
source_guide_idsNoIDs of existing projects to extract template data from

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / brand_locked
      Added value: +{
+  "description": "true: projects in this workspace built from this clueprint keep its own colors, fonts and logos instead of their brand kit's. Default false (re-skinned to the project's kit).",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / visibility / description
      Previous value: -"'private' = only you, 'workspace' = everyone in your workspace"New value: +"'workspace' shares it with your workspace; 'private' is stored as 'workspace'."
  3. Changed4 schema fields changed
    • removedInput schema / properties / context
      Removed value: -{
-  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
-  "type": "string"
-}
    • removedInput schema / properties / conversation_id
      Removed value: -{
-  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
-  "type": "string"
-}
    • removedInput schema / properties / llm_model
      Removed value: -{
-  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "visibility",
-  "context",
-  "llm_model"
-]New value: +[
+  "name",
+  "visibility"
+]
  4. Changed4 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
    • addedInput schema / properties / conversation_id
      Added value: +{
+  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
+  "type": "string"
+}
    • addedInput schema / properties / llm_model
      Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "visibility"
-]New value: +[
+  "name",
+  "visibility",
+  "context",
+  "llm_model"
+]
  5. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  6. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations mark this as a non-read-only, non-destructive creation tool, and the description adds substantial behavioral context: source-guide extraction can take minutes, decision lists in the reply should be surfaced to the user, and brand_locked changes whether projects retain the clueprint's branding. No annotation contradictions.

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-loads the definition and scope in the first sentence, then groups structural details, extraction behavior, decision handling, and brand_locked semantics into readable paragraphs. It is long but mostly earns its space for a complex creation tool; some inline enumerations make it denser than necessary.

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?

Given no output schema, the description explains the important reply behavior by naming the non-empty decision lists that must be surfaced to the user and recorded via update_clueprint. It also covers folder structure, extraction timing, and brand-locked behavior, leaving little ambiguity for an agent invoking this tool.

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. The description still adds meaningful semantic detail for brand_locked (including the co-marketing use case) and source_guide_ids (clip-by-clip extraction and latency), going beyond the schema's brief field descriptions.

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?

Starts with a specific verb and resource: "Create a new clueprint," then immediately defines a clueprint as a reusable video template with structured design notes, rules, and screenshots. It clearly distinguishes clueprints from projects by explaining the format versus brand-kit relationship.

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?

Explains when source_guide_ids triggers clip-by-clip extraction and tells the agent to ask the user about decision lists and record them with update_clueprint(decisions). It also clarifies the create_clueprint vs create_project distinction, but does not explicitly state when not to use this tool.

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

All Clueso 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