Skip to main content
Glama
Sign In

SnapDub

by ai.snapdub
OverviewDiscussionsAdmin

Clips of a video

list_clips
Read-onlyIdempotent

Lists a finished video's clips, best first: title, virality score (0-100), description, hashtags, length and a download link that expires in an hour.

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": {
      "video_id": "<video_id>"
    },
    "name": "list_clips"
  }
}

Input Schema

NameRequiredDescriptionDefault
video_idYesThe video_id from create_video or list_videos.
include_linksNoInclude each clip's download link. Defaults to true; set false when only titles and scores are needed - the links are long.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_links
      Added value: +{
+  "description": "Include each clip's download link. Defaults to true; set false when only titles and scores are needed - the links are long.",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: results are sorted best-first, and download links expire after one hour, which an agent must know before caching or sharing links.

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?

A single front-loaded sentence that lists only what matters: resource, ordering, fields, and the time-sensitive link caveat. No filler.

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?

With no output schema, the description carries the return-value burden and does so by enumerating fields and ordering. It omits pagination/result-size behavior, which is the only notable gap for a list tool.

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 coverage is 100%, so the baseline would be 3. The description adds meaning beyond the schema by explaining that the link expires in an hour and that scores range 0-100, which clarifies the semantics of the link-bearing output tied to include_links.

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?

States a specific verb and resource ('Lists a finished video's clips') and enumerates the returned fields plus ordering ('best first'). This is clearly distinct from siblings like get_video or list_videos, which operate on the video itself rather than its clips.

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?

The phrase 'a finished video's clips' implies the prerequisite that the video must be complete, and the schema note ('from create_video or list_videos') chains it after creation. No explicit when-not or alternative is given, but no sibling overlaps this function, so guidance is clear enough.

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

All SnapDub toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources