Skip to main content
Glama
long-video-mcp

long-video-mcp

by Ehmad9

project_report

Reports project progress by showing which segments have scripts and comparing estimated total runtime against the target duration.

Instructions

Report progress of a project: which segments have scripts, estimated total runtime versus the target.

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": "<project>"
    },
    "name": "project_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'Report' conveys that this is a non-mutating read, and the description usefully discloses the shape of what comes back (per-segment script coverage, runtime vs target), which substitutes partially for the missing output schema. It says nothing about cost, permissions, or behavior when the project has no scripts or no target set.

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 front-loaded sentence with a colon that enumerates the report contents; no filler, no restatement of the title.

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?

For a one-parameter read tool with no output schema, disclosing the report's contents covers much of the gap, but the identifier format for 'project' and error behavior remain undocumented, which is enough to matter at call time.

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?

One required parameter ('project') with 0% schema description coverage, and the description adds no meaning — it does not say whether the value is an ID, a name, or a path, nor what happens on an unknown project. The single most important ambiguity for invoking this tool is left unresolved.

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 ('Report progress of a project') and goes further by naming the content of the report: segments with scripts and estimated runtime versus target. That is clearly distinguishable from create_project, list_projects, or shot_list, though it never explicitly contrasts itself with a sibling.

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?

Usage is only implied by the purpose statement — an agent can infer you call this to check progress, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as list_projects.

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