Video Brief Manifest MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_video_briefA | Check a draft video brief for subject, motion, camera, visual-detail, and audio-direction signals. |
| build_video_brief_manifestC | Return a portable JSON manifest containing the brief, optional delivery constraints, and validation results. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one validates a video brief, the other builds a manifest from it. There is no overlap in their functions, so an agent can easily select the right tool.
Both tools follow a consistent verb_noun pattern: validate_video_brief and build_video_brief_manifest. The naming is predictable and reflects the action performed.
With only two tools, the server is on the low end of the typical range, but both tools are essential and complement each other for the server's narrow purpose. The count feels slightly thin but is appropriate for the specific task of validating and building a manifest.
The server covers the full workflow from validating a draft brief to generating the portable manifest. There are no obvious gaps in the stated purpose, as the two tools together provide a complete pipeline.