Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Update clip text

update_clip_text
Idempotent

Update the post text attached to a clip and change the text of any existing Scheduling post while preserving its scheduled time.

Instructions

Changes the post text that goes with a clip. If the clip already has a post in Scheduling, that post's text changes too (a scheduled post keeps its time).

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>",
      "text": "<text>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "update_clip_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
clip_idYesThe clip's id, from list_recordings or get_recording.
account_idNo
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

B3.3/5.0
Behavior3/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=true), the description discloses a genuinely non-obvious cascade: if the clip already has a post in Scheduling, that post's text is also changed while keeping its scheduled time. That is valuable side-effect disclosure. However, it says nothing about failure modes, whether empty text is allowed, or what happens to posts that have already been published, leaving the mutation's blast radius only partially characterized.

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?

Two sentences, front-loaded with the primary action and followed immediately by the conditional side effect. No filler, no restating of the name or annotations.

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 covers the key behavior an agent most needs to know (the scheduling cascade) and the tool has no output schema to explain. But for a four-parameter mutation with mostly undocumented parameters, it omits what the call returns, whether the text can be cleared, and what preconditions must hold, leaving an agent to guess on several practical points.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%: clip_id and account_id are documented in the schema, while text and idempotency_key carry no descriptions. The description adds a little meaning for text by framing it as 'the post text that goes with a clip' (i.e., the caption, not a transcript), but it says nothing about idempotency_key semantics or how retries are deduplicated, so it does not compensate for the coverage gap.

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 names a specific verb and resource: it 'Changes the post text that goes with a clip.' This distinguishes it from a generic update_post or update_clip_design, since the object being mutated (the clip's associated post text) is explicit. It does not, however, explicitly contrast itself with sibling updating tools, so the sibling differentiation is inferential rather than stated.

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?

Usage is implied rather than spelled out: an agent can infer it should call this when it wants to edit the caption accompanying a clip. No conditions for when not to use it, no prerequisites (e.g., clip must exist, permission scope), and no named alternatives 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