ChatCut

create_project

Create a new empty ChatCut project for the current external MCP user.

Use this when an external MCP client needs a fresh project before importing or editing media. This uses ChatCut's official Zero project.createWithTrack mutator, creates one active timeline and one video track, and returns the editor URL plus a liveProject card payload for the new project. For user-facing edit sessions, present that card/link immediately so the user can open it with the MCP host's Open in dropdown. Do not use Node REPL, Playwright, shell open, or system Chrome to open ChatCut unless the user explicitly asks for external-browser QA. Existing external MCP calls still need to pass that new projectId to target the new project.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_project"
  }
}

Input Schema

Name	Required	Description
`fps`	No	Defaults to 30.
`name`	No	Project display name. Defaults to External MCP No-Source E2E.
`description`	No
`editorBaseUrl`	No	Editor origin/base URL. Defaults to CHATCUT_EDITOR_URL or http://localhost:5173.
`compositionWidth`	No	Project width in pixels. Defaults to 1920.
`compositionHeight`	No	Project height in pixels. Defaults to 1080.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedNov 5, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes well beyond the annotations by naming the underlying mutator (project.createWithTrack), disclosing that one active timeline and one video track are provisioned, and describing the return payload (editor URL plus liveProject card). It also warns that the project is opened via the host's Open in dropdown rather than external browser tooling, and that downstream calls must retarget to the new projectId.

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 in the first sentence, followed by usage, behavior, and caveats in a logical order. A few sentences (the Open in dropdown and Node REPL/Playwright prohibition) are host-workflow guidance rather than tool semantics, which adds length but not much waste.

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 creation tool with no output schema, the description adequately covers what is built, what is returned, and how to surface the result. Overall fidelity to the tool's complexity is good.

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 description coverage is 83%, so defaults for fps, name, size, and editorBaseUrl are already documented in structured fields. The description adds no extra meaning about parameter effects or interactions, so the baseline applies.

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?

States a specific verb and resource ("Create a new empty ChatCut project") and pins the scope to the current external MCP user, which separates it from duplicate_project and edit_project in the sibling list. It further specifies the concrete artifact created: one active timeline and one video track.

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?

"Use this when an external MCP client needs a fresh project before importing or editing media" gives a clear triggering condition, and the follow-on note that existing MCP calls must pass the new projectId clarifies sequencing. It does not explicitly contrast against duplicate_project or restore_project, leaving that comparison to inference.

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

All ChatCut tools Inspect

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.