Skip to main content
Glama

Render shorts

render_short_from_project

Renders shorts as 9:16 MP4s with the brand's captions, hook title, logo, small print, music and end card: drafts at 720p to watch first, finals at 1080p (accepted shorts only; recorded in the project's exports). 15 credits a draft, 20 a final. Returns one task_id per short; get_task gives render_id and download_url in about 3 to 4 minutes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "moment_ids": "<moment_ids>"
    },
    "name": "render_short_from_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftNotrue: 720p to watch first; false: the 1080p final (accepted shorts only)
moment_idsYes
project_idYesFrom create_project

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, it discloses cost (15 credits a draft, 20 a final), the side effect (finals are recorded in the project's exports), the async contract (one task_id per short, get_task yields render_id and download_url in about 3-4 minutes), and the accepted-shorts precondition. That is exactly the operational context the annotations (readOnlyHint=false, idempotentHint=false) cannot convey.

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?

Two tightly packed sentences that front-load the output format and follow with cost and return behavior; no filler. The middle clause listing brand elements is long but each item earns its place by telling the agent what the render bakes in.

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 return contract itself (task_id, then get_task for render_id/download_url with a 3-4 minute expectation) and the cost and side-effect model. For a three-parameter async render tool, nothing material is missing.

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 coverage is 67%, and the description's draft explanation largely restates the schema's own description of the draft flag. It adds the useful implication that moment_ids is one entry per short (since one task_id is returned per short), but project_id and the maxItems=10 cap are left to the schema.

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 gives a concrete verb (renders) plus the resource and output format (shorts as 9:16 MP4s) and enumerates the composed elements (captions, hook title, logo, small print, music, end card). This clearly separates it from the long-form and promo render siblings without needing their schemas.

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 states a clear workflow rule: draft at 720p to watch first, final at 1080p only for accepted shorts. That tells the agent which mode to pick and what precondition gates the final render. It never names a sibling alternative such as render_long, so it stops short of explicit alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources