switch

Get Analysis Report

get_vision_report

Read-onlyIdempotent

Fetch one of your finished Video Analysis reports by report_id (from analyze_video_report or list_vision_reports). Returns the complete structured report: overview scores and takeaways, the timeline of scenes, audio, visual, story, speech, the recreation section with every master prompt, and metadata, plus recreation_prompt (the ready to run prompt) at the top level. While an analysis is still running this reports processing; poll it every 20 to 30 seconds.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`report_id`	Yes	The report id to fetch.

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description complements them by disclosing that the tool reports processing status and requires polling. It adds concrete behavioral context beyond the annotations with no contradictions.

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?

Two dense sentences cover purpose, return contents, and polling guidance with no wasted words. The structure front-loads the primary action and then adds necessary details, making it highly efficient.

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?

Given the single parameter and no output schema, the description thoroughly enumerates the returned report structure (scores, timeline, sections, metadata, recreation_prompt) and explains the polling behavior. It is fully complete for an agent to 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% but the parameter description is minimal ('The report id to fetch'). The description adds meaningful semantics by specifying the origin of report_id (from analyze_video_report or list_vision_reports) and its role in retrieving the report, going beyond the schema.

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 clearly states the tool fetches a finished Video Analysis report by report_id, with a specific verb ('Fetch') and resource. It distinguishes itself by referencing analyze_video_report and list_vision_reports as sources of the ID, making the purpose unambiguous.

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?

The description explains that report_id comes from analyze_video_report or list_vision_reports, and advises polling every 20-30 seconds while processing. This provides clear usage context without explicitly stating when not to use the tool, so a slight deduct is appropriate.

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

All switch 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.5/5.0

Disambiguation2/5

Several tools occupy nearly identical semantic ground: apply_iphone_realism and apply_ugc both describe casual phone-shot looks, upload_media and upload_reference_asset both accept uploads, and analyze_video overlaps heavily with analyze_video_report. The many apply_* style tools are essentially one tool parameterized by style, so agents can easily select the wrong one.

Naming Consistency4/5

Most tools follow a clear verb_noun snake_case pattern such as generate_image, list_my_videos, get_editor_run, and upscale_video. A few outliers like voice, talking_avatar_video, and video_to_prompt do not use the same verb-first convention, but they are still readable and do not create significant confusion.

Tool Count1/5

At 55 tools, the surface is far beyond what is appropriate for an MCP server; many of these be collapsed or parameterized, especially the 10 apply_* style wrappers and several overlapping upload/status helpers. Even for a broad media platform, this scale forces a huge context window and makes selecting the right tool impractical.

Completeness2/5

The surface covers generation, media display, video analysis, and Editor workflows well, but there are obvious gaps in library lifecycle management: move_asset and create_folder are referenced in tool descriptions without being exposed, and there is no clean way to delete or reorganize media assets. Agents following the descriptions will try to call tools that do not exist.

Resources

Need Help?