Skip to main content
Glama

clip_history

View previously created clips to prevent duplicate clips. Check existing clips before creating new ones.

Instructions

View previously created clips to avoid duplicates. Check before creating new clips.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results for list
actionYeslist = recent clips, check = find duplicate, delete = remove a clip
clip_idNoClip id, full or 8-char prefix (for delete)
end_secondNoEnd time (for check)
source_videoNoSource video path (for check or filter)
start_secondNoStart time (for check)
caption_styleNoCaption style (for check)
crop_strategyNoCrop strategy (for check)
Behavior3/5

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

No annotations provided, so description carries full burden. It only states purpose and action enumerations, missing details on side effects, rate limits, or state changes. Minimal but sufficient for basic use.

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?

Extremely concise with two short sentences, front-loaded with the key purpose. No wasted words.

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?

With 8 parameters, 1 required, and 1 enum, the description is minimal. It doesn't explain when to use specific actions like 'check' vs 'list' or how it relates to siblings like suggest_clips. The output schema is absent, but schema descriptions partially compensate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all parameters have descriptions in the schema. The tool description adds no additional semantics beyond the schema, meeting the baseline of 3.

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?

Description clearly states the tool views previously created clips to avoid duplicates, with a specific use case of checking before creating new clips. It distinguishes from sibling tools like create_clip and suggest_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?

Explicitly recommends using the tool before creating new clips to avoid duplicates, providing clear context. However, it doesn't mention when not to use it or provide explicit 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/nmbrthirteen/podcli'

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