Skip to main content
Glama
cloudglue

Cloudglue MCP Server

Official
by cloudglue

retrieve_summaries

Read-onlyIdempotent

Bulk retrieve video summaries and titles from a collection to understand its content and themes. Use this as your first step when analyzing a collection.

Instructions

Bulk retrieve video summaries and titles from a collection to quickly understand its content and themes. Works with both rich-transcripts and media-descriptions collections. Use this as your first step when analyzing a collection - it's more efficient than retrieving full descriptions and helps you determine if you need more detailed information. Perfect for getting a high-level overview of what's in a collection, identifying common topics, or determining if a collection contains relevant content for a specific query. For single videos, use describe_video instead. For targeted content discovery, consider using search_video_summaries (for relevant videos) or search_video_moments (for specific segments) instead of browsing through all summaries. Results are paginated in 25 summaries per page - use the 'page' parameter to retrieve specific pages (page 0 = first 25 summaries, page 1 = next 25 summaries, etc.). Each response includes page and total_pages fields. For comprehensive collection analysis, paginate through all summaries by incrementing the page parameter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYesCollection ID from list_collections. Works with both rich-transcripts and media-descriptions collections.
pageNoPage number for paginated results. Each page contains 25 summaries. Defaults to 0 (first page). Use this to retrieve summaries for specific pages. Increase the page number to get the next 25 summaries.
created_afterNoOnly include summaries created after this date (YYYY-MM-DD format, e.g., '2024-01-15'). Useful for analyzing recent additions to a collection.
created_beforeNoOnly include summaries created before this date (YYYY-MM-DD format, e.g., '2024-01-15'). Useful for analyzing historical content.
Behavior5/5

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

Annotations already mark it as read-only and idempotent, and the description adds pagination details (25 per page, page parameter, page and total_pages in response). This fully discloses behavior beyond annotations without contradiction.

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?

The description is well-structured and front-loaded: first sentence states purpose, then usage guidelines, alternatives, and pagination details. Every sentence adds distinct value; no fluff.

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, when to use, alternatives, pagination behavior, date filtering, and response fields (page, total_pages). No output schema, but the description sufficiently informs about return structure.

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?

The input schema has 100% description coverage, so the baseline is 3. The description adds value by explaining the 'first step' strategy for collection analysis and reinforcing pagination mechanics, going slightly beyond the 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?

The description clearly states the tool's purpose: bulk retrieving video summaries and titles from a collection. It distinguishes itself from siblings like describe_video (single videos) and search_video_summaries (targeted content discovery), leaving no ambiguity.

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

Usage Guidelines5/5

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

Provides explicit when-to-use guidance: 'first step when analyzing a collection' and 'more efficient than retrieving full descriptions'. Also specifies when not to use it (for single videos or targeted search) and names alternative tools (describe_video, search_video_summaries, search_video_moments).

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