Skip to main content
Glama

videogenie_project_list

List active video projects and optionally include archived records to manage project lifecycle and resume work.

Instructions

List active projects; explicitly include archived records when needed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "videogenie_project_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_archivedNo

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.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden, and it does add real behavioral value by stating the default filter (active projects only) and the archived-exclusion behavior. It says nothing about pagination, result limits, ordering, or that this is a non-destructive read, which for an unannotated tool leaves notable gaps.

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 compact sentence with the default scope front-loaded before the opt-in clause, and no filler. It is terse but every clause carries information.

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

Completeness4/5

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

The tool is simple (one optional boolean), an output schema exists so return values need no explanation, and the description covers the default scope plus the archived opt-in. Only secondary details such as pagination or ordering are absent, which is acceptable at this complexity.

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

Parameters4/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 the sole parameter, and it does: the flag explicitly includes archived records, which conveys both the meaning and the consequence of setting it. Syntax details are minor for a boolean with a default of false.

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 uses a specific verb and resource ("List ... projects") and pins down the default scope as active-only, which separates it from the sibling mutation tools (archive, create, rename, restore) whose names imply different operations. It stops short of explicitly naming any sibling as the alternative, so it is clear but not fully differentiated by reference.

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?

"explicitly include archived records when needed" gives a conditional cue for the opt-in case, implying the agent should call it plainly for normal listing and flip the flag only when archives matter. There is no statement of when not to use this tool or which sibling to prefer for a single-project lookup (e.g. the get tool), leaving routing partly to inference.

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