Skip to main content
Glama

Clueso

by io.clueso
OverviewDiscussionsAdmin

Get project data

get_project
Read-only

Get a summary of a project: canvas dimensions, per-clip summary (ids, indices, durations, element counts, voiceover_volume), and audio_tracks — every music/SFX entry on the project flattened to the same wire shape add_audio accepts (id, src, name, source_duration, guide_start_time/end_time, music_start_time/end_time, volume, loop, fade_in, fade_out). To copy an audio track to another project: read it from audio_tracks here and feed the same fields to add_audio on the target project. Call this to understand what's in the project before making changes. A clip whose voiceover this server is still generating carries duration_pending: true (with a top-level durations_pending note): its duration is the old value until the audio lands. get_clip says the same as duration_pending on any read that shows timings. Pass render to check the whole film in ONE image instead of the summary: {seams: true} every cut, {clips: true} one frame per clip (its middle; {clips: {at: 'start'|'middle'|'end'|}} for another moment), {at: [film seconds]}. get_clip's filmstrip {seam: true} zooms into one cut.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
renderNoThe whole film as ONE labelled image instead of the summary: exactly one of seams, clips or at. A reply that leaves cuts or clips out names the next from_cut or from_clip.
project_idYesThe project ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / render
      Added value: +{
+  "additionalProperties": false,
+  "description": "The whole film as ONE labelled image instead of the summary: exactly one of seams, clips or at. A reply that leaves cuts or clips out names the next from_cut or from_clip.",
+  "properties": {
+    "animations": {
+      "description": "false draws every element settled.",
+      "type": "boolean"
+    },
+    "at": {
+      "description": "Film seconds, at most 15.",
+      "items": {
+        "minimum": 0,
+        "type": "number"
+      },
+      "maxItems": 15,
+      "minItems": 1,
+      "type": "array"
+    },
+    "clips": {
+      "anyOf": [
+        {
+          "const": true,
+          "type": "boolean"
+        },
+        {
+          "additionalProperties": false,
+          "properties": {
+            "at": {
+              "anyOf": [
+                {
+                  "enum": [
+                    "start",
+                    "middle",
+                    "end"
+                  ],
+                  "type": "string"
+                },
+                {
+                  "minimum": 0,
+                  "type": "number"
+                }
+              ],
+              "description": "Where in each clip (default 'middle'), or clip seconds."
+            },
+            "from_clip": {
+              "description": "First clip shown (default 0).",
+              "maximum": 9007199254740991,
+              "minimum": 0,
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        }
+      ],
+      "description": "One frame per clip. 15 clips a call."
+    },
+    "max_width": {
+      "description": "Sheet width in px (default 1280).",
+      "maximum": 1568,
+      "minimum": 320,
+      "type": "integer"
+    },
+    "seams": {
+      "anyOf": [
+        {
+          "const": true,
+          "type": "boolean"
+        },
+        {
+          "additionalProperties": false,
+          "properties": {
+            "from_cut": {
+              "description": "First cut shown (default 0).",
+              "maximum": 9007199254740991,
+              "minimum": 0,
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        }
+      ],
+      "description": "Every cut: the last frame before it and the first after, labelled with its transition. 7 cuts a call."
+    }
+  },
+  "type": "object"
+}
  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.5/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses genuinely non-obvious behavior: clips mid-voiceover-generation carry duration_pending:true with a top-level durations_pending note and a stale duration value, plus the pagination contract that a truncated reply names the next from_cut/from_clip. Those are the traits that change how an agent interprets timings and continues a read, and they are not derivable from the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the core purpose, which is good, but it degenerates into one very dense run-on that nests the render explanation, cross-tool advice and pending-duration caveat together. It also restates constraints already in the schema verbatim ('at most 15', '7 cuts a call'), spending words on structured data.

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?

With no output schema, the description carries the full burden of describing returns and does so thoroughly: summary fields, the exact audio_tracks wire shape matching add_audio, the pending-duration flag, and what the render image mode produces. Nothing an agent needs in order to call or interpret this tool is missing.

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 baseline is 3, but the description adds a real constraint the schema does not enforce: the render mode is 'exactly one of seams, clips or at', and it clarifies how the per-clip {at: 'start'|'middle'|'end'|<seconds>} moments map onto the render output. Only the mode semantics are added, so it is above baseline but not exhaustive.

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?

Opens with a specific verb+resource and enumerates exactly what the summary contains (canvas dimensions, per-clip summary, flattened audio_tracks), so an agent knows the payload shape without opening anything else. It also differentiates from siblings by naming add_audio and get_clip and describing the get_project/get_clip division of labor.

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?

"Call this to understand what's in the project before making changes" gives clear context, and the audio-copy recipe explicitly routes the agent (read audio_tracks here, feed to add_audio on the target). It also carves out get_clip's filmstrip {seam:true} for cut zooming. It stops short of stating when NOT to use this tool (e.g. use get_clip for a single clip's timings), so no explicit exclusion.

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