Skip to main content
Glama

create_edit

Create a new edit (project) in a workspace. Before planning a new multi-step project, discover and load a matching workflow with list_sequencer_skills and get_sequencer_skill, and consult get_model_catalog modelSelectionGuidance. Aspect ratio is required because it controls every generated shot; use 9:16 for vertical/social films unless the user asks for another format. Defaults are Nano Banana 2.1 (google-nano-banana-2-1) for still images, Gemini Omni 1.2 Flash (google-gemini-omni-1-2) for videos, and Cartesia Sonic 3.6 (cartesia-sonic-3-6) for speech. Returns the new edit ID.

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": {
      "workspaceId": "<workspaceId>",
      "title": "<title>",
      "aspectRatio": "<aspectRatio>"
    },
    "name": "create_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesTitle for the new edit
aspectRatioYesRequired project aspect ratio. Use 9:16 for vertical/social films unless the user explicitly asks otherwise.
workspaceIdYesThe workspace ID
defaultImageModelNoDefault still-image model ID. Defaults to Nano Banana 2.1 (google-nano-banana-2-1).
defaultVideoModelNoDefault video model ID. Defaults to Gemini Omni 1.2 Flash (google-gemini-omni-1-2).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / defaultVideoModel / description
      Previous value: -"Default video model ID. Defaults to Gemini Omni 1.1 Flash (google-gemini-omni-1-1)."New value: +"Default video model ID. Defaults to Gemini Omni 1.2 Flash (google-gemini-omni-1-2)."
  2. Changed1 schema field changed
    • changedInput schema / properties / defaultImageModel / description
      Previous value: -"Default still-image model ID. Defaults to Nano Banana Pro (google-gemini-3-image)."New value: +"Default still-image model ID. Defaults to Nano Banana 2.1 (google-nano-banana-2-1)."
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose useful behavior: aspectRatio is required because it governs every generated shot, default models are applied when omitted, and the call returns the new edit ID. It stops short of stating side effects such as credit consumption, permission requirements, or whether creation is reversible.

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?

Creation is stated first, then prerequisites, then the required-parameter rule and defaults, then the return value — a sensible front-loaded order. It is denser than necessary, repeating model names alongside their IDs and mentioning a speech model that no parameter accepts.

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?

For a 5-parameter creation tool with no output schema, the description covers purpose, prerequisites, the mandatory field's rationale, defaults and the return value, which is nearly everything an agent needs. Gaps are the unexplained speech default and the absence of any side-effect or permission disclosure.

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 the baseline is 3, but the description adds rationale beyond the schema by explaining why aspectRatio is mandatory and naming the concrete default model for stills, video and speech. The speech model has no corresponding parameter in the schema, which slightly muddies the mapping.

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 first sentence states a specific verb and resource ('Create a new edit (project) in a workspace'), including a clarifying gloss that 'edit' means 'project'. An agent can distinguish this from siblings such as update_edit, get_edit and create_workspace immediately.

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?

Explicit sequencing guidance: load a matching workflow via list_sequencer_skills and get_sequencer_skill before planning a multi-step project, and consult get_model_catalog modelSelectionGuidance. It also gives a concrete rule for the aspect ratio choice (9:16 unless the user asks otherwise).

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.