Skip to main content
Glama
long-video-mcp

long-video-mcp

by Ehmad9

rename_segment

Assign a descriptive title to a video segment, replacing generic labels so YouTube chapter timestamps are meaningful.

Instructions

Give a segment (e.g. 'Chapter 2') a real title. Titles are used for YouTube chapter timestamps.

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>",
      "order": "<order>",
      "title": "<title>"
    },
    "name": "rename_segment"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderYesSegment number from the structure
titleYesNew title
projectYesProject name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 burden for what is clearly a mutation of stored project data. It discloses one useful downstream effect (titles drive YouTube chapter timestamps) but says nothing about whether the rename overwrites an existing title, whether it requires the segment to exist, or whether timestamps must be regenerated afterward.

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?

Two short sentences, front-loaded with the action, with zero filler. The phrasing 'a real title' is slightly informal but conveys that the current value is a placeholder, which is useful information rather than padding.

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 simple three-parameter mutation with no output schema, the description covers the what and the why but omits prerequisites, failure conditions (invalid segment number), and the consequence of renaming after timestamps were generated. Adequate but with clear gaps given zero annotation coverage.

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 100%, so all three parameters (project, order, title) are already documented in the schema and the baseline of 3 applies. The example 'Chapter 2' loosely illustrates what a segment/title pair looks like, but the description adds no meaning about the 'order' numbering or project scoping beyond the schema text.

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 states a concrete verb and resource — give a segment a title, with an example ('Chapter 2') that clarifies what a segment is. It does not name a sibling tool or explain how it differs from generate_timestamps, which is the closest-looking neighbor, so it stops short of full differentiation.

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: the note that titles feed YouTube chapter timestamps hints at the context in which to call it. There is no explicit when-to-use or when-not-to-use rule, and no statement of whether a structure must already exist (e.g. from plan_structure) before renaming.

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