videogenie-mcp

by jasonfaria84-rgb

Overview Schema Source Related Servers Discussions Admin

Python

Local

videogenie_project_create

Create a persistent video project with an initial storyline, or replay the original creation via an idempotency key.

Instructions

Create a persistent project and initial storyline, or replay the original key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "videogenie_project_create"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`idempotency_key`	Yes

Output Schema

Name	Required	Default
`data`	No
`error`	No
`success`	Yes
`project_id`	No
`request_id`	No
`storyline_id`	No
`schema_version`	No	1

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

B3/5.0

Behavior3/5

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

With no annotations, the description still conveys two real behavioral facts: the project is persistent (so it survives across jobs) and a call with an existing key replays rather than duplicates. It omits anything about side effects, whether a storyline is always generated, permissions, or error conditions.

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?

One short sentence with the primary action front-loaded, which is good structure. However, the second clause is ambiguous filler phrasing that costs more in confusion than it returns in information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A create-mutation with no annotations, no parameter descriptions, and a meaningful idempotency contract that is only glancingly described. The existence of an output schema excuses omitting return values, but the description still leaves too much unsaid for a tool that spawns persistent state.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden. 'Replay the original key' is the only hint about idempotency_key and is too vague to explain what constitutes a matching key, while 'name' gets no semantic guidance at all beyond its 1-200 length constraints.

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?

States a specific verb and resource ('Create a persistent project and initial storyline'), which distinguishes it from the sibling read/rename/archive tools. The trailing clause 'or replay the original key' muddies the purpose by describing a return-path behavior as if it were a second mode of the tool.

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?

Usage is only implied: creating a project is obviously the entry point before project_get/rename/archive, but the description never says when to create a new project versus reusing one, nor when the replay path applies. No alternatives or preconditions are named.

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

Deploy Server