Skip to main content
Glama
Sign In

Clueso

by io.clueso
OverviewDiscussionsAdmin

Export project

export_project

Start a video export of the project. Returns immediately with an export_id; the export renders in the background (~5 min) and the user gets the result in the editor's Exports tab. Start it, tell the user it has started (with the export_id), and stop: do not call get_export in a loop or hold run_script open waiting for it. Call get_export only when the user asks for the link (it then returns download_url, or embed_url for destination="embed").

destination: • "download" (default) — an mp4 file; once done, get_export returns a time-limited download_url. • "embed" — publish the project as an embeddable video player (the same embed the editor's Share → Embed creates). The embed URL is permanent: re-publishing after edits updates the video behind the SAME URL, so pages and LMS lessons that embed it update in place. Use get_embed(project_id) to read the URL and iframe code of an already-published project without re-rendering.

format: • "mp4" (default) — the video. • "mp3" — the project's whole soundtrack as one MP3: voiceover, music, extracted audio and video audio, mixed as the video plays them. Billed like a video export. Download only; resolution, fps and captions are ignored. There is no voiceover-only file: to leave music or video audio out, mute or remove it first.

Defaults: 1080p / 30fps / no captions / English. Pass overrides only when needed; a resolution or fps above the workspace's plan is capped to it. Refused while a job (speech, sync, the build) still holds the project, since the render would catch it mid-change: export once they finish. captions burns subtitles into a download; an embed instead carries captions the viewer toggles in the player, so captions is ignored for destination="embed".

Input Schema

NameRequiredDescriptionDefault
fpsNoFrames per second (default 30)
formatNo"mp4" (video, default) or "mp3" (the whole soundtrack, no picture; download only)
captionsNoBurn subtitles into the video (default false)
languageNoLanguage code of the voiceover and captions to render, e.g. 'de' for a translated project (default 'en'). Downloads only.
project_idYesThe project ID to export
resolutionNoOutput resolution (default 1080p)
destinationNoWhere the render goes: "download" (mp4 file, default) or "embed" (publish/update the project's embeddable player; its URL never changes). Publishing an embed needs an editor or admin role.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / format / description
      Previous value: -"\"mp4\" (video, default) or \"mp3\" (the voiceover alone; download only)"New value: +"\"mp4\" (video, default) or \"mp3\" (the whole soundtrack, no picture; download only)"
  2. Changed1 schema field changed
    • addedInput schema / properties / format
      Added value: +{
+  "description": "\"mp4\" (video, default) or \"mp3\" (the voiceover alone; download only)",
+  "enum": [
+    "mp4",
+    "mp3"
+  ],
+  "type": "string"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
+  "description": "Language code of the voiceover and captions to render, e.g. 'de' for a translated project (default 'en'). Downloads only.",
+  "minLength": 2,
+  "type": "string"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / destination
      Added value: +{
+  "description": "Where the render goes: \"download\" (mp4 file, default) or \"embed\" (publish/update the project's embeddable player; its URL never changes). Publishing an embed needs an editor or admin role.",
+  "enum": [
+    "download",
+    "embed"
+  ],
+  "type": "string"
+}
  5. 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"
+]
  6. 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"
+]
  7. Changed5 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
    • addedInput schema / properties / fps / anyOf
      Added value: +[
+  {
+    "const": 24,
+    "type": "number"
+  },
+  {
+    "const": 30,
+    "type": "number"
+  },
+  {
+    "const": 60,
+    "type": "number"
+  }
+]
    • removedInput schema / properties / fps / enum
      Removed value: -[
-  24,
-  30,
-  60
-]
    • removedInput schema / properties / fps / type
      Removed value: -"number"
  8. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Goes well beyond the annotations (readOnly=false, openWorld=true, destructive=false): returns immediately with an export_id, renders ~5 min in background, is refused while a speech/sync/build job holds the project, and resolution/fps above plan are silently capped. The one gap is that it never says what happens to a previously existing export or whether repeated calls stack up jobs.

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-loaded with the imperative workflow instruction, then bulleted per-parameter sections — good structure and almost no waste. It is long, but given 7 parameters with non-obvious interactions the length is largely earned; a few clauses (the "no voiceover-only file" aside) could be tightened.

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 still tells the agent what comes back (export_id immediately; download_url or embed_url later via get_export), covers defaults, plan caps, and the exact precondition that causes refusal. Nothing needed to call it correctly is missing.

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?

Schema coverage is already 100%, but the description still adds real semantics: destination="embed" is permanent and updates in place behind the same URL (with an editor/admin requirement), format="mp3" is download-only and ignores resolution/fps/captions, and captions are ignored entirely for embeds. That is behavior no schema enum can express.

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 ("Start a video export of the project") and immediately scopes the behavior as asynchronous. It also differentiates itself from siblings it could be confused with (get_export, get_embed, run_script) rather than leaving the agent to infer the boundary.

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?

Explicitly prescribes the correct agent behavior (start it, tell the user, stop) and names the anti-pattern to avoid — polling get_export or holding run_script open. It also states the condition for the follow-up call ("Call get_export only when the user asks for the link") and routes already-published projects to get_embed 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