Skip to main content
Glama

videogenie_project_archive

Archive a video project at its current revision while preserving its identity and full history, using the project ID and expected revision to guard against conflicting changes.

Instructions

Archive at the current revision, preserving identity and history.

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_archive"
  }
}

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.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and 'preserving identity and history' is the only behavioral claim. It does not say whether archiving is reversible, whether it removes the project from listings, what permissions are required, or what happens if expected_revision does not match — all critical for a mutation tool.

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 short sentence with the key qualifier ('at the current revision') front-loaded and no filler. It is efficient, though efficiency here comes partly at the cost of the detail the 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?

The output schema covers return values, but for a two-parameter mutation with zero annotation coverage the description is too thin: no failure modes, no idempotency or reversibility statement, and no parameter explanation. An agent could call it, but not confidently predict the consequences.

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 must explain both parameters, but it only alludes to revision through 'at the current revision'. It never explains that expected_revision is an optimistic-concurrency guard or what happens on mismatch, and project_id is not addressed at all.

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

Purpose3/5

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

The verb 'Archive' is clear and the tool name supplies the resource (project), so an agent can roughly infer the action. However, the description never explicitly says it archives a project, and it gives no differentiation from the sibling videogenie_project_restore, which is the obvious inverse operation an agent would need to weigh.

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?

There is no statement of when to archive versus when to use restore, rename, or leave the project alone, and no prerequisites or exclusions are given. The only usage-adjacent hint is 'at the current revision', which is not framed as guidance.

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