Simpler.Asia

studio.create_social_clip

Make one short as a NEW studio project from a range of an existing project: the finished scenes in the range are trimmed copies (no footage is generated or billed again), the captions move with them and the new project takes the target preset's shape. The source project is not changed. Free. Use the start_ms, end_ms and composition_version from studio.suggest_social_clips. Calling again within 24 hours with the same range, preset and version returns the same project (replayed: true) instead of a second copy; after 24 hours the same call makes a new project. Refuses, creating nothing: a composition_version that is no longer current (409 SIMPLER_STUDIO_CLIPS_STALE_VERSION names the current version; suggest again or resend with it), the same short made within 24 hours whose project was since deleted (409 SIMPLER_STUDIO_CLIPS_EARLIER_SHORT_GONE; move start_ms or end_ms by a few milliseconds to make it again), a range outside one stretch of finished footage or outside 5 to 60 s (shorter still when the preset's own limit is lower), read-only tokens and viewer roles. Next: video.export_create with the returned project_id and the same preset.

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>",
      "start_ms": "<start_ms>",
      "end_ms": "<end_ms>"
    },
    "name": "studio.create_social_clip"
  }
}

Input Schema

Name	Required	Description
`title`	No	Optional name for the new project (a suggestion's title).
`end_ms`	Yes	Where the short ends on the source timeline, in milliseconds (a suggestion's end_ms).
`start_ms`	Yes	Where the short starts on the source timeline, in milliseconds (a suggestion's start_ms).
`project_id`	Yes	The source studio project (vp_...) the suggestion came from.
`target_preset`	No	The export preset the short is for (default shorts_9x16); the new project takes its shape.
`composition_version`	No	The source composition_version the range was chosen on (the suggest result carries it). When the source has changed since, nothing is created and the answer names the current version.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With readOnlyHint=false only, the description carries the full burden and does so richly: no footage is generated or billed, the source project is untouched, 24-hour idempotent replay returns the same project (replayed: true), and each refusal is tied to a named 409 error code. This is far beyond what the single annotation conveys.

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-loads purpose and the non-billing guarantee, then idempotency, then refusal conditions, then the next step — a logical order with no filler. It is dense and the 409-code enumeration is heavy, but each sentence carries actionable information.

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?

For a mutation tool with no output schema, the description supplies what an agent needs: the returned project_id/replayed flag, billing implications, permission prerequisites, failure modes with recovery, and the follow-up call. Nothing essential to correct invocation is missing.

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 already 100%, so baseline is 3; the description adds real meaning by binding start_ms/end_ms/composition_version to their origin in the suggest result and explaining that composition_version reflects the composition the range was chosen on. It also suggests shifting by a few milliseconds to bypass a duplicate, which the schema does not convey.

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 output ("Make one short as a NEW studio project") plus the source ("from a range of an existing project"), and distinguishes the result from the precursor (studio.suggest_social_clips) and successor (video.export_create). An agent can tell exactly what this creates without opening the 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?

Explicitly tells the agent to take start_ms, end_ms and composition_version from studio.suggest_social_clips, and names the next step (video.export_create with the returned project_id and same preset). It also gives when-not conditions (stale version, range outside finished footage or 5–60 s, read-only tokens/viewer roles).

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?