Skip to main content
Glama
cloudglue

Cloudglue MCP Server

Official
by cloudglue

list_videos

Read-onlyIdempotent

Browse and search video metadata using filters for date, collection, and pagination. Returns essential video info like duration and filename.

Instructions

Browse and search video metadata with powerful filtering options. Use this to explore available videos, find specific content by date, or see what's in a collection. Returns essential video info like duration, filename, and IDs needed for other tools. Results are paginated in 25 videos per page - use the 'page' parameter to retrieve specific pages (page 0 = first 25 videos, page 1 = next 25 videos, etc.). Each response includes page and total_pages fields. Use date filtering to focus on specific time periods, then paginate within those results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for paginated results. Each page contains 25 videos. Defaults to 0 (first page). Use this to retrieve videos for specific pages. Increase the page number to get the next 25 videos.
collection_idNoFilter to videos in a specific collection. Use the collection ID from list_collections. Leave empty to see all user videos.
created_afterNoOnly show videos created after this date. Format: YYYY-MM-DD (e.g., '2024-01-15'). Useful for finding recent content.
created_beforeNoOnly show videos created before this date. Format: YYYY-MM-DD (e.g., '2024-01-15'). Useful for filtering to older content.
Behavior4/5

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

Annotations already indicate read-only and non-destructive. The description adds valuable details about pagination (25 per page, page/total_pages fields) and response content, which exceeds what annotations provide.

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?

The description is efficient with no redundant sentences. It front-loads the main purpose and filters, then explains pagination. A minor trade-off for completeness, but very well structured.

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?

Given no output schema, the description adequately explains response fields (page, total_pages, duration, filename, IDs) and usage pattern. It covers filtering and pagination, making it complete for the tool's 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 has 100% coverage, but the description adds context beyond field descriptions, such as pagination mechanics (page 0 = first 25) and the presence of total_pages in response. This extra guidance aids correct usage.

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?

The description clearly states it is for browsing and searching video metadata, and distinguishes itself from sibling tools like describe_video and get_video_metadata by focusing on listing multiple videos with filtering.

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 clear context for when to use (explore, find by date, collection), and hints at pagination workflow. However, it does not explicitly state when not to use or name 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