Skip to main content
Glama

videogenie_project_get

Retrieve a video project by its explicit project ID, including its retained archived state, so agents can inspect or resume project work.

Instructions

Read an explicit project ID, including retained archived state.

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": {
      "project_id": "<project_id>"
    },
    "name": "videogenie_project_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
successYes
project_idNo
request_idNo
storyline_idNo
schema_versionNo1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It does add one genuinely useful behavioral fact — that archived projects remain readable ('including retained archived state'), meaning archived items are not filtered out — but it says nothing about what happens for a missing/deleted ID, permission requirements, or whether archived results are flagged in the response.

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?

A single short sentence with the core action front-loaded and no filler. Every clause — the read action, the ID scope, and the archived-state note — contributes information.

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

Completeness3/5

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

The tool is simple (one required param) and has an output schema, so return values need no explanation. However, with no annotations and no schema descriptions, the description should have covered the ID format and error behavior for unknown IDs; the archived-state note is the only supplementary detail present.

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

Parameters3/5

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

The single parameter has 0% schema description coverage, so the description is the only source of parameter meaning, and it adds only that the ID is 'explicit' (i.e., a known identifier rather than a name or filter). It gives no format, length, or provenance detail for project_id, leaving the agent to guess at valid input.

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 a specific verb and resource ('Read ... project ID'), so an agent can tell this is a single-project fetch rather than a list or job lookup. The phrasing 'Read an explicit project ID' is slightly awkward compared to 'retrieve a project by ID', and it does not explicitly name the sibling it contrasts with (videogenie_project_list), but the intent is unambiguous.

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?

The word 'explicit' implies this is for when you already hold a known project ID, as opposed to browsing via videogenie_project_list, but that contrast is never stated and no alternative tool is named. There is no guidance on what to do when the ID is unknown or when a list-based lookup would be more appropriate.

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