Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Change clip design

change_clip_design
Idempotent

Re-render a clip with a new design while keeping the current video live until the draft post updates; published clips cannot change, and scheduled clips require confirmation.

Instructions

Re-renders one clip in a different design (template). The current video stays in place until the new one is ready, then the clip's draft post is updated. A published clip cannot be changed. If the clip's post is scheduled, it comes off the schedule: the first call then changes nothing and returns needs_confirmation, will_happen and confirmation, the change happens only on a second call with that confirmation, and unscheduled_post gives the time it had.

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": {
      "clip_id": "<clip_id>",
      "design_id": "<design_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "change_clip_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
clip_idYesThe clip's id, from list_recordings or get_recording.
design_idYesA design id from list_recording_designs.
account_idNo
confirmationNo
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the old video persists until the new one is ready, that the draft post is updated in place, that published clips are immutable, and that scheduled posts are pulled off schedule. It also documents the two-call confirmation protocol and the fields returned by the first call (needs_confirmation, will_happen, confirmation, unscheduled_post), which the annotations do not cover.

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?

Front-loaded with the core action and free of filler; each clause adds a new behavioral fact. The final sentence is long and chains several conditions, which costs some readability, but no sentence is expendable.

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?

With no output schema, the description does the heavy lifting for return values by naming the confirmation-flow fields. What's missing is only the success-path response shape and any note on rendering duration, which are minor for a well-annotated mutation tool.

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 40%, so the description needs to carry weight; it does explain the confirmation parameter's round-trip semantics and mentions unscheduled_post. However, idempotency_key is left entirely unexplained in both schema and description, and the relationship between clip_id/design_id is already covered by 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 first sentence names a specific verb and resource ('Re-renders one clip in a different design') and scopes it to a single clip, which cleanly separates it from siblings like update_clip_text or set_default_recording_design. An agent can tell what the tool does without opening the schema.

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?

It gives concrete preconditions for use: the clip must not be published, and if the post is scheduled the operation is gated behind a confirmation handshake. There is no explicit routing to a named alternative for the blocked published/scheduled cases, so it stops just short of full when/when-not guidance.

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