Skip to main content
Glama

Clueso

by io.clueso
OverviewDiscussionsAdmin

Update project

update_project

Update a project's metadata: rename, change description, move to a different folder, or change aspect ratio.

Only fields you provide are changed. To move a project to the workspace root, pass folder_id="" (empty string).

Aspect ratio: pass any "W:H" (positive integers). The canvas is fit inside 1920×1080 keeping the ratio, so element pixel coordinates use the resulting canvas. Common values:

  • "16:9" → 1920×1080 (landscape, YouTube/web — default)

  • "9:16" → 608×1080 (portrait — TikTok/Reels/Shorts)

  • "1:1" → 1080×1080 (square — Instagram feed)

  • "3:4" → 810×1080 (portrait card)

  • "4:5" → 864×1080 (portrait — Instagram feed)

Element coordinates are stored as fractions of the canvas, so existing elements reflow to the new canvas automatically — no element coordinates are rewritten.

Tags: add_tags / remove_tags change the project's tags (the home page Tags menu and filter), by NAME. Adding a name the workspace doesn't have creates it; existing names match ignoring case. List them with find(type='tags'). Only workspace editors and admins can change tags. To tag many projects, loop update_project over their ids in run_script. When tags are given, the reply also has tags (the project's full list after the change), created_tags and not_found_tags (remove_tags names the workspace doesn't have).

Concurrency: whole-project mutation (conflict domain: the entire project) — serialize. Do not run it in parallel with ANY other mutation on the same project_id, including element/voiceover edits; run them one at a time. (Mutations to different projects run in parallel freely.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoNew project title
add_tagsNoTag names to add; missing tags are created.
folder_idNoNew folder ID. Pass '' (empty string) to move to workspace root.
project_idYesThe project ID to update
descriptionNoNew description
remove_tagsNoTag names to remove.
aspect_ratioNoNew aspect ratio as 'W:H' (positive integers). Common: '16:9' landscape, '9:16'/'4:5'/'3:4' portrait, '1:1' square.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / add_tags
      Added value: +{
+  "description": "Tag names to add; missing tags are created.",
+  "items": {
+    "maxLength": 40,
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / remove_tags
      Added value: +{
+  "description": "Tag names to remove.",
+  "items": {
+    "maxLength": 40,
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}
  2. 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: -[
-  "project_id",
-  "context",
-  "llm_model"
-]New value: +[
+  "project_id"
+]
  3. 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: -[
-  "project_id"
-]New value: +[
+  "project_id",
+  "context",
+  "llm_model"
+]
  4. 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
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say it is a non-read-only, non-destructive, closed-world mutation. The description goes far beyond: partial-update semantics ('only fields you provide are changed'), the canvas fitting math and the guarantee that existing elements reflow rather than being rewritten, tag auto-creation and case-insensitive matching, the editor/admin permission requirement, and the exact response fields (tags, created_tags, not_found_tags). It also states a hard concurrency contract: serialize against any other mutation on the same project_id.

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?

Purpose is front-loaded and the sections (partial update, aspect ratio, tags, concurrency) are each doing distinct work. The five-row aspect-ratio table is the longest block, but every row carries a different canvas size and use case, so it is informative rather than padded; a slightly tighter layout would be ideal.

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 7-parameter mutation with no output schema, the description covers what an agent needs: partial-update behavior, special sentinel values, permission requirements, tag side effects, the response shape for tags, and the serialization rule against concurrent mutations. Nothing material is left to inference.

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 description coverage is 100%, so the baseline is 3, but the description adds real meaning: the aspect-ratio table maps each 'W:H' value to the concrete canvas it produces (e.g. '9:16' → 608×1080), and it clarifies that tag operations match by NAME and create unknown names. This goes beyond the schema's pattern and one-line hints.

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 opening sentence gives a specific verb (update), the exact resource (a project's metadata), and enumerates the mutable surfaces: rename, description, folder, aspect ratio, plus a tags section. An agent can immediately separate this from update_elements, update_clips, or duplicate_project without opening a schema.

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?

It provides concrete routing guidance: use find(type='tags') to list tags, loop update_project inside run_script to tag many projects, and pass folder_id="" for the workspace root. It also implicitly warns that element/voiceover edits are separate mutations. What is missing is an explicit statement of when to prefer a sibling (e.g. create_project or update_elements) instead.

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