AskEditor

Create new project

create_editor_project

[write] A new project in your workspace, optionally opening on a library file (from list_media or an upload) as its first clip. Only when the person asks for a new project or has none. A project holds a board (script, scenes, generated images and video) and a timeline, so never make a second one for the same film: work in the project they opened or named. When you already have a project in hand it is refused unless person_asked is true. Returns project_id, title, kind, and its links as get_editor_url gives them.

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": {
      "title": "<title>"
    },
    "name": "create_editor_project"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	The project's name.
`aspect_ratio`	No	Optional: the canvas's shape; default 9:16.
`person_asked`	No	True only when the person asked, in their own words, for a new project. Needed when you are already working in one. Never set it to get past a refusal: ask them.
`workspace_id`	No	Optional: which workspace; default your default workspace.
`source_asset_id`	No	Optional: a library file to open the project on, as its first clip.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already establish write/non-idempotent/non-destructive, and the description adds genuinely new behavior: the tool is refused if a project is already active unless person_asked is true, and it states the return payload (project_id, title, kind, links). It stops short of describing side effects such as whether an empty board is auto-populated or what happens to the workspace's existing projects.

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 write marker and the core action, then the guardrails, then the return shape — a sensible order. It is dense but nearly every clause carries a constraint; the parenthetical about board contents is the only slightly padded part.

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?

No output schema exists, and the description compensates by naming the returned fields and deferring link format to get_editor_url. Combined with the creation guard and the project-vs-project distinction, an agent has everything needed to call it correctly or avoid calling it.

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; the description still adds routing value by tying source_asset_id to list_media or an upload and by reinforcing that person_asked is a truthful attestation, not an override. It does not add format or default detail beyond the schema, which the schema already covers.

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 bracketed write marker and a specific verb+resource: creates a new project in the workspace, optionally seeded from a library file as its first clip. It also delineates the resource's contents (board + timeline), which lets an agent distinguish it from open_project or list_projects without opening a schema.

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 when-to-use: 'Only when the person asks for a new project or has none.' Explicit when-not: never create a second project for the same film, work in the one the person opened or named. It also documents the refusal condition when a project is already in hand, which is exactly the alternative-selection signal an agent needs.

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

All AskEditor 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.

Resources

Need Help?