capcut-mcp

capcut_open

Open a CapCut page in your signed-in Cloud Browser to work with export and share drafts; default URL is https://www.capcut.com.

Instructions

Open a CapCut page in your signed-in Cloud Browser (default https://www.capcut.com) to work with export and share drafts.

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

Input Schema

Name	Required	Description	Default
`url`	No	Page to open. Default: https://www.capcut.com

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 13, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a valuable behavioral fact — the page opens inside a 'signed-in' Cloud Browser session, implying authentication is pre-established — plus the default target URL. However, it says nothing about whether this navigates the current tab, replaces an existing page, or what state is returned after opening.

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?

One front-loaded sentence with the action first and the purpose last; no filler. It could be marginally tighter since the default URL appears twice across description and schema, but nothing is wasted.

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?

For a one-optional-parameter navigation tool with no output schema, the description supplies the essential context: the environment (signed-in Cloud Browser), the default target, and the intended workflow. Only the post-open state and any URL restrictions are missing, which are minor for this complexity level.

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% for the single optional 'url' parameter, so the baseline is 3. The description's restatement of the default (https://www.capcut.com) duplicates the schema rather than adding format hints such as whether relative paths or non-CapCut URLs are accepted.

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?

States a specific verb ('Open') and resource ('a CapCut page in your signed-in Cloud Browser'), which is enough to separate it from siblings like capcut_click or capcut_read that act on an already-open page. The added purpose clause about export and share drafts narrows it further. It stops short of explicitly naming the sibling it precedes.

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 clause 'to work with export and share drafts' implies the scenario where this tool belongs, but there is no explicit when/when-not guidance, no statement that this should be called before capcut_click/capcut_type, and no note on behavior if a CapCut page is already open.

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

Deploy Server