Skip to main content
Glama
cloudglue

Cloudglue MCP Server

Official
by cloudglue
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

segment_video_chapters

Idempotent

Segment videos into chapters with cost-optimized detection. Returns timestamps and descriptions for each chapter from any supported URL source.

Instructions

Segment videos into chapters with intelligent cost optimization. Automatically checks for existing chapter segmentation jobs before creating new ones. Returns timestamps and descriptions for each chapter detected. Supports all URL formats: Cloudglue URLs, YouTube URLs, public HTTP video URLs, and data connector URLs (Dropbox, Google Drive, Zoom).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesVideo URL to segment into chapters. Supports multiple formats: • **Cloudglue platform (default)**: `cloudglue://files/file-id` - Use file ID from list_videos • **YouTube URLs**: `https://www.youtube.com/watch?v=...` or `https://youtu.be/...` • **Public HTTP video URLs**: Direct links to MP4 files (e.g., `https://example.com/video.mp4`) • **Data connector URLs** (requires setup in Cloudglue account): - **Dropbox**: Shareable links (`https://www.dropbox.com/scl/fo/...`) or `dropbox://<path>/<to>/<file>` - **Google Drive**: `gdrive://file/<file_id>` - **Zoom**: Meeting UUID (`zoom://uuid/QFwZYEreTl2e6MBFSslXjQ%3D%3D`) or Meeting ID (`zoom://id/81586198865`) See https://docs.cloudglue.dev/data-connectors/overview for data connector setup.
promptNoCustom prompt to guide chapter detection. Describe what types of chapters or segments you want to identify. Examples: 'Identify main topics and transitions', 'Find scene changes and key moments', 'Segment by speaker changes and topics'. Leave empty to use default chapter detection.

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Discloses automatic job checking (supports idempotency hint), cost optimization, and return of timestamps/descriptions. No contradiction with annotations.

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?

Concise and front-loaded with main purpose. Every sentence adds value without redundancy.

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

Completeness5/5

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

Covers all key aspects: purpose, supported URL types, duplicate prevention, and return values. Adequate given no output schema.

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 covers 100% of parameters with detailed descriptions. The tool description adds context about cost optimization and duplicate checking, providing extra value beyond schema.

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

Purpose5/5

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

Clearly states the tool segments videos into chapters with cost optimization. Distinguishes from sibling tools like segment_video_camera_shots by specifying chapter segmentation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides context on when to use (for chapter segmentation) and mentions duplicate detection. However, does not explicitly state when not to use or compare with alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cloudglue/cloudglue-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server