Skip to main content
Glama

Clueso

by io.clueso

Create project

create_project

Create a new blank Clueso project. Returns the projectId and initialClipId — the project starts with one blank clip already at index 0 (default short duration). Use update_clips to resize/retitle clip 0, add_clips(kind='blank') to append more clips, add_elements to place content, and add_audio to attach a project-level music track.

Optionally place the project inside a folder (use find(type='folders') to find folder IDs) and set a description at creation time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoProject title
folder_idNoOptional folder ID to nest the project under. Use find(type='folders') to discover IDs. Omit to create at workspace root.
descriptionNoOptional project description (max ~500 chars)

TDQS

A4.2/5.0
Behavior4/5

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

The description discloses behavioral details beyond annotations: the project starts with one blank clip at index 0 with default short duration, and the tool returns projectId and initialClipId. Annotations already indicate mutation (readOnlyHint=false) and non-destructiveness, so the description adds useful context about initial state and return values.

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?

The description is concise with three sentences: first states purpose and return, second lists follow-up tools, third covers optional folder and description. It is front-loaded, every sentence adds value, and there is no redundant information.

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?

Given the tool has 3 optional parameters and no output schema, the description covers initial state, return values, and post-creation workflow. It does not explain potential constraints (e.g., title uniqueness) or error cases, but for a simple creation tool, the coverage is reasonably complete and actionable for an AI agent.

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 100%, so the baseline is 3. The description adds some value by explaining the folder_id context (use find to discover IDs, omit for root) and mentioning description at creation, but these are largely redundant with the schema descriptions. No additional semantic depth is provided beyond what the schema already offers.

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 clearly states 'Create a new blank Clueso project' with a specific verb and resource. It distinguishes from sibling tools by outlining post-creation steps (update_clips, add_clips, etc.), implying this tool is for initial creation only. The return values (projectId and initialClipId) are also specified.

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?

The description provides explicit guidance on when to use this tool (for initial creation) and references sibling tools (update_clips, add_clips, add_elements, add_audio) for subsequent actions. It also advises on folder placement using find(type='folders'). However, it does not explicitly state when not to use it (e.g., for duplicating a project), though this is implied by the listed alternatives.

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

A4.1/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but there is notable overlap between remove_elements and remove_from_project(target='element'), which both remove elements from a clip. This duplication could cause an agent to misselect. Otherwise, tools like add_clips, add_elements, add_audio, and analyze_audio are well-differentiated.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (e.g., add_clips, create_project, get_clip, update_elements). There are no camelCase or mixed conventions. Even compound names like voiceover_batch and auto_sync fit the pattern. This makes the tool set predictable for an agent.

Tool Count2/5

With 40 tools, the set is significantly larger than the 3-15 range that typically earns its place. While the domain of video creation is broad, several tools seem redundant (remove_elements vs remove_from_project) or narrowly scoped (get_design_guide, get_element_schema), inflating the count. The number feels heavy for the apparent scope.

Completeness4/5

The tool surface covers most lifecycle operations: create, read, update, delete for projects, clips, elements, audio, articles, and clueprints. Minor gaps exist, such as no explicit tool to delete a voiceover (only mute via update_clips) and no folder management beyond listing. Overall, agents can accomplish full workflows with few workarounds.

Resources