Skip to main content
Glama
Sign In
Arkeonix CapCut MCP

Arkeonix CapCut MCP

by daviilpzDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

capcut_apply_pip_layout

Apply a Picture-in-Picture or split-screen preset to a selected clip in a CapCut draft, adjusting scale for corner placements. Choose from corner and split positions to set the clip layout.

Instructions

Apply Picture-in-Picture or Split-Screen layout preset to a clip.

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": {
      "draft": "<draft>",
      "segmentId": "<segmentId>",
      "layout": "<layout>"
    },
    "name": "capcut_apply_pip_layout"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftYes
scaleNoscale for corner PiP (default: 0.35)
layoutYesPiP or split-screen preset
segmentIdYestarget video/image segment ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral disclosure burden. It only says 'Apply...', implying in-place mutation, but does not disclose whether the draft is modified immediately, whether persistence requires capcut_save, whether existing layout settings are overwritten, or how scale interacts with corner presets beyond the schema default.

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 front-loaded sentence with no filler or redundant detail. It communicates the essential action and scope efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a mutation tool with four parameters, no annotations, and no output schema, yet the description only states the action. It omits persistence semantics, side effects, the optional scale caveat, and any comparative guidance against sibling layout-related operations, leaving the agent under-informed for reliable invocation.

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?

The schema already provides descriptions for layout, scale, and segmentId (75% coverage), so the description does not need to repeat them. However, the description adds no new parameter meaning, and the required 'draft' parameter remains undocumented in both the schema and the description, leaving a small gap that the description does not fill.

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 states a specific action ('Apply'), a specific resource type ('layout preset'), and a target ('clip'). It clearly distinguishes this from sibling apply_* tools by naming the preset kind as Picture-in-Picture or Split-Screen, leaving no ambiguity about the tool's purpose.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus the many sibling apply_* tools (effect, transition, animation, filter, mask, etc.), nor does it mention prerequisites, ordering, or alternatives. Usage context must be entirely inferred from the tool name.

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