Skip to main content
Glama
Sign In

switch

by ai.switchapp
OverviewDiscussionsAdmin

Full Video Analysis

analyze_video_report

Run the FULL Switch Vision analysis on a video, the same premium report the Video Analysis page produces: it watches AND listens in three forensic passes and returns a structured report with every category: overview (scores and takeaways), a second by second timeline, audio, visual craft, story and retention, speech transcript, ready to run recreation prompts, and metadata. Pass video_url (a public https video URL, YouTube included) OR one of your own Switch video ids. For an external file also pass duration_seconds (YouTube and your own videos are measured automatically) because the analysis is billed per second of the file, 3 tokens per second with a 30 second minimum. Re-running the same video and question returns the existing report without charging again. Optional question focuses the analysis. Returns a report_id right away; poll get_vision_report until status is succeeded (a few minutes). If it cannot finish, your tokens are returned automatically. For one quick question about a video use analyze_video instead; this tool is the full paid report. PRICE: Priced by the length of the file (see above); the same video and question again is free. Pass quote_only: true first to get the exact price; nothing is made and nothing is charged. To run it (not for a quote) send video_url.

Input Schema

NameRequiredDescriptionDefault
forceNoOptional. Re-running the same video and question returns the existing report without charging again; pass true to force a fresh, freshly billed analysis.
questionNoOptional. Something to pay special attention to.
video_urlNoA public https video URL (YouTube ok), OR one of your own Switch video ids.
quote_onlyNotrue answers the price only: nothing is made and nothing is charged.
duration_secondsNoLength in seconds. Required for external files; YouTube and your own Switch videos are measured automatically.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / quote_only
      Added value: +{
+  "description": "true answers the price only: nothing is made and nothing is charged.",
+  "type": "boolean"
+}
    • removedInput schema / required
      Removed value: -[
-  "video_url"
-]
  2. Changed1 schema field changed
    • addedInput schema / properties / force
      Added value: +{
+  "description": "Optional. Re-running the same video and question returns the existing report without charging again; pass true to force a fresh, freshly billed analysis.",
+  "type": "boolean"
+}
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, openWorldHint=true; the description adds the substantive behavior an agent actually needs: billing at 3 tokens/second with a 30-second minimum, idempotent re-runs that don't recharge, force=true to re-bill, automatic token refund on failure, and the fact that nothing is produced or charged under quote_only.

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-loaded with the core action and report contents, and every section carries real information. Minor redundancy: the price model is stated twice (mid-paragraph and again in the 'PRICE:' block), including the repeated 'same video and question again is free' line, which could be consolidated.

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?

No output schema exists, so the description carries the return contract — it states a report_id comes back immediately and that the agent must poll get_vision_report until status is succeeded. For a 5-parameter paid async tool, the price, refund, caching, and polling details make it callable without further inference.

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 this is additive context rather than compensation. The description explains why duration_seconds matters (billing is per second), what quote_only is for as a first step, that question focuses the analysis, and that force triggers a fresh billed run — all meaningfully beyond the field labels.

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 resource ('run the FULL Switch Vision analysis on a video') and enumerates exactly what the report contains (overview, timeline, audio, visual craft, story/retention, transcript, prompts, metadata). It explicitly distinguishes itself from the sibling analyze_video ('for one quick question ... use analyze_video instead').

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?

Gives explicit routing to the alternative (analyze_video for a single quick question), states the two input paths (public https URL / own Switch video id), the requirement to pass duration_seconds for external files, the async polling recipe, and the recommended quote_only-first workflow. When-to-use and when-not-to-use are both covered.

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

All switch toolsInspect
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