Simpler.Asia

studio_project_create

Create a video studio project — the composition document (scenes, tracks, clips, captions) starts empty and is built up afterward through the studio.* director tools. thumbnail_key is server-owned: send thumbnail_data_url instead, and this door externalizes it into a content-addressed R2 key through the media hygiene kit (magic bytes decide the type; SVG refuses). Free. NEXT: studio_project_read to verify.

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": "studio_project_create"
  }
}

Input Schema

Name	Required	Description
`name`	No
`status`	No
`thumbnail_key`	No
`thumbnail_data_url`	No	Data URL (data:image/...) of the project thumbnail — the door externalizes it into a content-addressed R2 key through the media hygiene kit (magic bytes decide the type; SVG refuses). Never send thumbnail_key directly; it is server-owned and computed from this field. Omit to leave the thumbnail unset/unchanged.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 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: it discloses that the composition starts empty, that thumbnail_key is server-owned and derived from thumbnail_data_url, that externalization uses content-addressed R2 keys with magic-byte type detection and SVG rejection, and that creation is free. That is real behavioral context an agent cannot infer from readOnlyHint/destructiveHint.

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 and the next-step pointer is at the end, which is good ordering. Phrasing like 'this door' and 'media hygiene kit' is colorful but still carries information, though it adds slight density.

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 4-parameter create tool with no output schema, the description covers the empty-initial-state, thumbnail handling, cost, and verification path. Only the status field and any permission/scope requirements remain unaddressed.

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?

With only 25% schema coverage the description should compensate, but it only elaborates on the thumbnail params — and that explanation largely duplicates the already-present thumbnail_data_url schema description. The 'name' and 'status' parameters (including the status enum values) get no added meaning, so it is only partially compensating.

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 concrete verb+resource ('Create a video studio project') and immediately disambiguates scope: the composition document starts empty and is populated later via studio.* tools, which separates it from studio_project_read/update. An agent knows exactly what this tool produces.

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?

Explicitly names the follow-on action ('NEXT: studio_project_read to verify') and the downstream tool family (studio.* director tools) for building content. It stops short of stating when NOT to use it (e.g. duplicate/import paths), so 4 rather than 5.

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

All Simpler.Asia 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?