Skip to main content
Glama
Sign In
Arkeonix CapCut MCP

Arkeonix CapCut MCP

by daviilpzDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

capcut_list_animations

Search CapCut's 800+ animation catalog by type, keyword, or target element. Filter in, out, loop, group effects for video or text, with optional cached-only results and limit.

Instructions

Search CapCut animations catalog (~800+ entries: in, out, loop, group for video or text).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "capcut_list_animations"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoanimation direction/type
limitNomax results to return (default: 20)
queryNosearch keyword (e.g. "zoom", "fade", "slide", "bounce")
cachedOnlyNoonly return animations cached locally
targetTypeNotarget element type (video or text)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden of explaining behavior. It discloses the catalog size and supported categories, which is useful, but it does not mention that this is a read-only listing operation, describe the return format, or clarify any caching/network behavior implied by the cachedOnly parameter. The description is not misleading, but it leaves behavioral details to inference.

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 a single focused sentence that front-loads the action and includes meaningful scope details. There is no filler, redundancy, or unnecessary content.

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?

The description is adequate for selecting the tool and understanding its domain, but because there is no output schema, it leaves the return shape unspecified. An agent would benefit from knowing what fields are returned (e.g., animation IDs/names) and how results relate to capcut_apply_animation.

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 the schema already documents all five parameters and their roles. The description adds only catalog-level context and repeats categories already present in the type enum, so it does not materially enhance parameter understanding 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 uses a specific verb ('Search') and resource ('CapCut animations catalog'), and clearly scopes the catalog by categories ('in, out, loop, group for video or text'). This distinguishes it from sibling list tools like capcut_list_effects and capcut_list_transitions.

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

Usage Guidelines3/5

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

The description implies the tool is for discovering available animations, likely before applying one with capcut_apply_animation, but it does not explicitly state when to use it versus alternatives or when not to use it. No exclusions or alternative routing are provided.

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

Deploy Server

Other Tools