Skip to main content
Glama
cloudglue

Cloudglue MCP Server

Official
by cloudglue

describe_video

Idempotent

Describe videos from YouTube, Cloudglue, and direct URLs. Automatically reuses existing descriptions to save costs, and paginates results in 5-minute segments.

Instructions

Gets comprehensive video descriptions with intelligent cost optimization and pagination support. Automatically checks for existing descriptions before creating new ones. Supports YouTube URLs, Cloudglue URLs, and direct HTTP video URLs with different analysis levels. Results are paginated in 5-minute segments - use the 'page' parameter to retrieve specific time segments of longer videos (page 0 = first 5 minutes, page 1 = next 5 minutes, etc.). Use 'start_time_seconds' to begin pagination from a specific time index (defaults to 0 for start of video). The combination of start_time_seconds and page allows precise navigation: start_time_seconds sets the base offset, and page increments in 5-minute segments from that offset. When collection_id is provided (from a media-descriptions collection), this tool fetches previously extracted descriptions that were stored in that collection for the given Cloudglue file, saving time and cost. Use this for individual video analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesVideo URL to describe. 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.
collection_idNoOptional collection ID to fetch previously extracted media descriptions from a media-descriptions collection (saves time and cost). Use collection ID from list_collections without. When provided with a Cloudglue URL, this tool retrieves existing descriptions that were previously extracted and stored in the specified collection. Only works with Cloudglue URLs.
pageNoPage number for paginated results. Each page contains 5 minutes of video content. Defaults to 0 (first page). Use this to retrieve descriptions for specific time segments of longer videos. Increase the page number to get the next 5-minute segment. Works in conjunction with start_time_seconds - page 0 starts from start_time_seconds, page 1 starts 5 minutes after start_time_seconds, etc.
start_time_secondsNoStarting time offset in seconds for pagination. Defaults to 0 (start of video). Use this to begin pagination from a specific time index in the video. Combined with the page parameter, this allows you to navigate to specific time ranges: start_time_seconds sets the base offset, and page increments in 5-minute segments from that offset. For example, start_time_seconds=600 (10 minutes) with page=0 returns content from 10-15 minutes, page=1 returns 15-20 minutes, etc.
Behavior5/5

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

Discloses automatic check for existing descriptions before creation, aligning with idempotentHint=true. Adds behavioral details on pagination and cost optimization beyond annotations, with no contradictions.

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?

Front-loaded with purpose, then details. Slightly verbose but each sentence adds necessary context, covering URL types, pagination, and collection workflow. Could be trimmed without losing clarity.

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?

Covers pagination and collection reuse well, but lacks details on the output format (structure of descriptions) and mentions 'different analysis levels' without elaboration. Without an output schema, the description should provide more on return values.

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 descriptions. The tool description adds value by explaining the combined use of start_time_seconds and page for precise navigation, and the purpose of collection_id, going beyond the schema's inline descriptions.

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 'Gets comprehensive video descriptions' with specific verb+resource. Distinguishes from sibling tools like get_video_metadata and extract_video_entities by focusing on descriptions with pagination and cost optimization.

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?

Specifies 'Use this for individual video analysis' and explains when to use collection_id to save time/cost. Lacks explicit alternatives or when-not-to-use guidance, but context is clear from sibling tool names.

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