framesail

Update project

update_project

Patch project fields. Updatable: title, description, sfx_level, video_concept, voice_mix, voice_tts_provider, script_target_minutes, narrator_speed, video_format. (The narrator's TTS voice is NOT here — use set_narrator_voice.)

narrator_speed is the narration rate (0.5-2.0, default 1.0; clamped to
0.7-1.2 on ElevenLabs). It changes how fast words are SAID and nothing
else — it adds no silence between them, so "slow this down" usually
wants `<break>` tags in the script text too (see save_script).

video_format ('landscape' | 'portrait') is only changeable until the
storyboard exists — after that the shots and overlays are composed for the
current frame and the patch 409s. Switch it before generate_storyboard.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`fields`	Yes	Partial dict of fields to patch; allowed keys: title, description, sfx_level ('none'\|'minimal'\|'frequent'), video_concept, voice_mix ('narrator_only'\|'narrator_led'\|'balanced'\|'character_led'), voice_tts_provider ('minimax'\|'elevenlabs'), script_target_minutes, narrator_speed, video_format
`project_id`	Yes	Project ID, as returned by create_project or list_projects

TDQS

A5/5.0

Behavior5/5

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

Annotations only indicate the tool is not read-only, not idempotent, and not destructive, so the description carries the behavioral burden. It reveals non-obvious behavior: narrator_speed clamped to 0.7-1.2 on ElevenLabs, no silence insertion, video_format 409s after storyboard exists, and the need for script break tags for slower pacing.

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 structured into focused paragraphs, each earning its place: updatable fields list, narrator_speed nuance, and video_format constraint. There is no filler or repetition of schema boilerplate.

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?

The description is complete for invocation: it covers all fields, exclusions, constraints, and cross-tool pointers to set_narrator_voice, save_script, and generate_storyboard. No output schema exists, but for a patch operation the provided behavioral and scheduling context is sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 100% schema description coverage, the description adds practical semantics beyond the schema: enumerates allowed field keys, gives the narrator_speed range and default, explains what narrator_speed does and does not affect, and clarifies video_format's enum and modification window.

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 states a specific action, 'Patch project fields', and explicitly lists every updatable field. It also distinguishes itself from a sibling by noting the narrator TTS voice is not here and belongs to set_narrator_voice.

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?

Provides explicit when-not-to-use guidance: narrator TTS voice is excluded and routed to set_narrator_voice. It also gives a lifecycle constraint for video_format and advises switching before generate_storyboard, and points to save_script for silence/break tags.

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?