Skip to main content
Glama

videogenie_project_rename

Rename an active video project only if it is still at the expected revision, preventing overwrites of concurrent changes.

Instructions

Rename an active project only at its 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>",
      "name": "<name>",
      "expected_revision": "<expected_revision>"
    },
    "name": "videogenie_project_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
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

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose two meaningful traits beyond structured fields: the project must be active, and the mutation only applies at the current revision (a stale-write guard). It omits what happens on a revision mismatch (error type, retry semantics), permission requirements, and whether the rename is reversible.

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?

One front-loaded sentence with no wasted words; the constraint follows the action immediately. It is on the edge of over-terseness, since the active/revision conditions could each use one clarifying clause, but nothing is redundant.

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?

An output schema exists, so return values need no explanation, and the core preconditions are stated. For an unannotated mutation tool, however, the failure mode on revision mismatch and the permission model remain unaddressed, leaving the agent to guess how to recover from a stale-revision error.

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

Parameters5/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 compensate — and "at its current revision" is precisely the semantics of expected_revision: it must equal the project's current revision, not an arbitrary version number. That single phrase converts an opaque integer into a concurrency token, which the schema alone does not convey. project_id and name are self-evident from their titles.

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 ("Rename ... project") and adds a scope qualifier ("an active project"). It is clearly distinct from archive/create/get/list/restore siblings by operation, though it never names or contrasts an alternative.

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?

"only at its current revision" implies a precondition that the caller must first obtain the current revision (presumably via videogenie_project_get), but this is only implied. There is no explicit when-to-use/when-not guidance, no mention of the required read-before-write sequence, and no mention of the archived-project alternative (restore) when a project is not active.

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