Vixdeo — Tu Productor IA

Read Video Blueprint

get_project_vbp

Read-onlyIdempotent

The Video Blueprint of a project's CUT — the version that edits change and the production line renders (the structured score of scenes) — plus cast.voicePin: the voice named when the piece was created, the row it names, which rows narrate each scene and whether the pin was honored. Paged so every answer fits the size a host accepts for one tool result: without scene_from the answer carries the piece-level fields and as many scenes as fit, from scene 0; with scene_from (and optionally scene_count) it carries only that window of scenes. page says where the page starts, how many scenes the piece has, nextSceneFrom (null on the last page) and whether the answer holds the whole blueprint (complete). Scene positions are 0-based, the same positions the edit ops take, and so is every reference to a scene inside the blueprint (score, chapters, colour, thumbnail): sceneReferences states the base and, per group, whether those references were verified. Each scene's factual_backing.artefactos lists the researched facts the scene cites, each with its id in the piece's material (A7 a fact, N3 an anecdote), its source and URL; pantalla says whether a screen is documentada, reconstruida (labelled) or retenida (content absent from the declared sources was withheld). A scene's duration_target_sec is the window written before the voice exists: the render fits each scene to its narration, so those windows add up to more than the delivered video, whose measured length the project status reports as finalVideoDurationSec. Each page also carries fidelity: the per-scene rows of the project status's fidelityReport for the scenes of that page. Org-isolated: a project outside the caller's organization is not found. $0.

Input Schema

TableJSON Schema

Name	Required	Description
`project_id`	Yes	The project id.
`scene_from`	No	0-based position of the first scene of the page (`page.nextSceneFrom` of the previous answer). Without it the answer is the first page, which also carries the piece-level fields.
`scene_count`	No	Optional: at most this many scenes. The page may carry fewer when they would not fit in one result.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

changedInput schema / properties / scene_from / description

Previous value: -"0-based position of the first scene of the page (`page.nextSceneFrom` of the previous answer). Omit it for the first page, which also carries the piece-level fields."New value: +"0-based position of the first scene of the page (`page.nextSceneFrom` of the previous answer). Without it the answer is the first page, which also carries the piece-level fields."

Changed2 schema fields changedSep 27, 2026

addedInput schema / properties / scene_count

Added value: +{
+  "description": "Optional: at most this many scenes. The page may carry fewer when they would not fit in one result.",
+  "type": "integer"
+}

addedInput schema / properties / scene_from

Added value: +{
+  "description": "0-based position of the first scene of the page (`page.nextSceneFrom` of the previous answer). Omit it for the first page, which also carries the piece-level fields.",
+  "type": "integer"
+}

First observedSep 27, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations already declare a safe, idempotent, closed-world read, and the description still adds substantial behavior: org-scoped lookups ('a project outside the caller's organization is not found'), paging semantics with complete/nextSceneFrom flags, 0-based indexing shared with edit ops, and a $0 cost note. This is rich context well beyond the annotation surface.

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

Conciseness3/5

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

It is front-loaded with the resource definition, but the prose is a dense single block of em-dash clauses that is hard to parse, and several field explanations (artefactos, pantalla, duration_target_sec) run long. Given there is no output schema the detail is defensible, yet the structure is tangled rather than economical.

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?

With no output schema, the description carries the full burden of explaining returns and does so thoroughly — page structure, scene references and their bases, factual backing, fidelity rows, duration semantics, and pagination behavior. Combined with annotations and fully documented parameters, an agent has what it needs to call this 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 baseline is 3, but the description adds meaning: it ties scene_from to the prior answer's page.nextSceneFrom and explains that omitting it also returns the piece-level fields, and notes scene_count may be reduced to fit one result. That is genuine value on top of the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact resource it retrieves — the project's Video Blueprint of the CUT (the structured scene score) plus cast.voicePin data — and distinguishes it from the pieces of the system it borrows from (edit ops positions, the project status's fidelityReport). It is a noun-phrase inventory rather than a verb-led statement, and the sibling list is only differentiated implicitly, but an agent can tell what it gets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives detailed mechanics for the paging parameters (no scene_from = first page with piece-level fields; with scene_from = a window) and notes the org-isolation constraint. It never states when to reach for this over get_project_status or the list_* siblings, so selection guidance is implied rather than explicit.

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

All Vixdeo — Tu Productor IA 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?