Skip to main content
Glama
Sign In
capcut-mcp

capcut-mcp

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

capcut_guide

Get step-by-step guidance for CapCut screens, sign-in links, and exporting or sharing drafts before starting other CapCut tasks.

Instructions

How to work in CapCut (export and share drafts): its screens and the sign-in link. Call this first.

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_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in CapCut, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the behavioral burden. It implies a read-only informational tool and names the topics it covers, but does not state the return format (prose guidance vs. link list) or what happens if the task parameter is omitted.

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?

Two short sentences with the ordering instruction front-loaded and no padding. The parenthetical ('its screens and the sign-in link') is slightly cryptic in isolation but the total size is well matched to a simple guide tool.

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?

For a one-optional-parameter, no-output-schema tool, the definition covers purpose and ordering, but omits what the response contains and whether the task parameter is required for useful output. Adequate, but a sentence on the returned content would make it complete.

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 coverage is 100% and the single 'task' parameter is documented in the schema, so the description does not need to compensate. It adds no meaning beyond the schema, which is the expected baseline when the schema is self-sufficient.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the resource (CapCut workflow guidance) and scopes it to export/share drafts, screens, and the sign-in link, which distinguishes it from the UI-action siblings (click, type, open, read). The phrasing 'How to work in CapCut' is somewhat abstract, but the parenthetical narrows it enough for an agent to recognize it as an orientation/guide tool.

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?

'Call this first' gives an explicit ordering instruction that no sibling tool can satisfy. There are no when-not conditions or named alternatives, but for a first-step guide tool the invocation context is clear.

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