framesail

Create style

create_style

Create a style. Two mutually exclusive paths:

References (best): inputs=[{"input_type": "youtube" | "text", "value":
"<url or description>"}] — YouTube videos are watched (a channel link or
@handle resolves to that channel's newest usable upload) and text
directions read; async analysis writes the style's art/narrative/director
fields: await_jobs(style_id=...) before using the style. (Image/video FILE
references require the multipart REST endpoint POST /styles.)

Presets (instant, no analysis): presets={"art_style": id,
"narrative_style": id, "director_style": id} — all three axes, ids from
list_style_presets.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Display name for the style
`inputs`	No	Reference material to analyze, [{"input_type": "youtube" \| "text", "value": "<url or description>"}]; a youtube value can be a video link or a channel link/@handle (resolved to that channel's newest usable upload). Triggers an async analysis job. Mutually exclusive with presets
`presets`	No	Preset IDs per axis, {"art_style": id, "narrative_style": id, "director_style": id}, from list_style_presets; instant, no analysis. Mutually exclusive with inputs
`channel_id`	Yes	ID of the channel to create the style in, from list_channels

TDQS

A4.9/5.0

Behavior5/5

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

With minimal annotations (only readOnlyHint=false, destructiveHint=false), the description carries the full burden and succeeds: it discloses mutual exclusivity of inputs/presets, async analysis behavior for references, instant execution for presets, channel/@handle resolution semantics, and a note about REST-only file uploads. This goes far beyond the annotations and adds critical behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured, front-loaded with the core purpose, and every sentence adds information. The two-path breakdown with examples is economical and readable despite the length, with no filler or repetition of schema content.

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 creation tool with async behavior, no output schema, and two mutually exclusive input modes, the description covers prerequisites, sequencing (await_jobs), alternative REST endpoint, and required IDs from sibling tools. It is fully actionable for an agent to select and invoke the tool correctly.

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. The description enhances this by providing a concrete example structure for inputs and presets, explaining that presets require all three axes (art, narrative, director), and noting that channel/@handle resolves to the newest usable upload. These details go beyond the schema's field descriptions.

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 description opens with 'Create a style'—a specific verb and resource—and then details two distinct creation paths (references and presets), clearly distinguishing this from sibling tools like update_style_fields, analyze_style, and get_style. The scope is unambiguous and well-differentiated.

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?

The description explicitly states when to use each path ('References (best)' vs 'Presets (instant)'), mentions the need to call await_jobs before using the style, and explains that file references require the multipart REST endpoint, effectively guiding the agent away from this tool for those cases. It also references list_style_presets as a prerequisite source.

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

All framesail tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation3/5

Several tool families overlap in purpose, such as await_jobs/get_workflow_status/get_pipeline_progress, update_segment_content/update_segment_prompts, director_note/project_director_note, and scan_script/rescan_voice_blocks. The descriptions do a good job distinguishing them, but an agent must read carefully to avoid misselection, and there are more than a couple of confusable pairs.

Naming Consistency4/5

The set overwhelmingly follows a verb_noun snake_case convention with clear prefixes like get_, list_, set_, update_, create_, and delete_. Minor exceptions such as director_note, project_director_note, browse_audio_library, and whoami keep it from being perfectly consistent.

Tool Count1/5

At 72 tools, this is far beyond the 50+ extreme range and creates a heavy navigation burden for an agent. Even though the pipeline is complex, this many tools is not well-scoped for an MCP surface.

Completeness4/5

The surface covers the full script-to-export pipeline: styles, assets, voices, storyboards, segments, scenes, and rendering all have substantial lifecycle support. Some gaps exist—no delete_channel, delete_segment, delete_voice_block, or delete_provider_key—but most missing operations can be worked around through existing tools.

Resources

Need Help?