Skip to main content
Glama

videogenie_project_restore

Restore an archived video project by ID at its expected current revision to recover the project for continued management.

Instructions

Restore the same archived project ID at the current revision.

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>",
      "expected_revision": "<expected_revision>"
    },
    "name": "videogenie_project_restore"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
expected_revisionYes

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

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it omits the essentials for a mutating restore: whether restore is idempotent, what happens on revision mismatch, whether a new revision is produced, and whether prior data is recovered or dropped. "At the current revision" gestures at revision semantics without explaining them.

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?

A single tight sentence with no filler, but the phrase "the same archived project ID" assumes prior conversational context that a cold caller lacks, and brevity here comes at the cost of the details a mutating tool needs.

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?

For a mutating tool with no annotations and undocumented parameters, the definition is thin: no failure modes, no revision-conflict behavior, and no state-change outcome. An output schema exists, which relieves it of explaining return values, but not of explaining the restore contract.

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?

Schema coverage is 0%, so the description must compensate; it does mention the project ID and revision concepts, but "at the current revision" conflicts with the required `expected_revision` input, which reads as an optimistic-concurrency token. The description never explains that concurrency/validation role, leaving both parameters only nominally covered.

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?

Names a specific verb ("Restore") and resource ("archived project ID"), which distinguishes it reasonably well from the get/list/create/rename siblings. The trailing phrase "at the current revision" muddies rather than sharpens the purpose, and no sibling is explicitly named as the inverse operation.

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

Usage Guidelines2/5

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

No statement of when to use this versus archive/create/rename, and no prerequisite is given (e.g., that the project must currently be archived, or what happens if it is not). The intended context is only weakly implied by the word "archived".

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