Skip to main content
Glama

editor text set

editor_text_set
DestructiveIdempotent

Create or revise one title or text overlay with explicit timing. Revision checked; dryRun previews by default. This edits project text, not spoken audio or captions.

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": {
      "itemId": "<itemId>",
      "text": "<text>",
      "textKind": "<textKind>",
      "spec": "<spec>",
      "startSeconds": "<startSeconds>",
      "durationSeconds": "<durationSeconds>",
      "workspaceId": "<workspaceId>",
      "idempotencyKey": "<idempotencyKey>",
      "projectId": "<projectId>",
      "expectedRevision": "<expectedRevision>",
      "dryRun": "<dryRun>"
    },
    "name": "editor_text_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes
textYes
dryRunYes
itemIdYes
textKindYes
projectIdYesUUID string.
workspaceIdYes
startSecondsYes
idempotencyKeyYes
durationSecondsYes
expectedRevisionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / textKind / enum
      Previous value: -[
      -  "overlay",
      -  "title_card"
      -]New value: +[
      +  "overlay",
      +  "title_card",
      +  "lower_third"
      +]
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds two things not in them: a revision check (optimistic concurrency via expectedRevision) and the fact that dryRun defaults to preview. That default materially changes the risk profile of a destructive tool and is the most valuable sentence here. It stops short of saying what a rejected revision returns or what a real (non-dryRun) write destroys.

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?

Three short sentences, no filler, with the core action and the timing constraint front-loaded and the domain exclusion and safety default following in priority order. Every sentence carries distinct information.

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?

An output schema exists, so return values need not be described, and the safety default is covered. But for an 11-required-parameter destructive mutation with 9% schema coverage, the description leaves the create-vs-revise semantics (what a null itemId means) and the contents of `spec` unexplained, which an agent needs before calling correctly.

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 only 9% across 11 required parameters, so the description carries heavy burden. It conveys meaning for the timing pair ("explicit timing"), expectedRevision ("Revision checked"), dryRun ("previews by default"), and roughly textKind ("title or text overlay"), but says nothing about itemId vs projectId, workspaceId, idempotencyKey, or the shape of the opaque `spec` object, and never states the create-vs-revise rule.

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 set ("Create or revise") and a specific resource ("one title or text overlay") with scope (single item, explicit timing). It also draws a boundary against adjacent domains ("not spoken audio or captions"), which separates it from captions_* and editor_audio_set. It does not, however, distinguish itself from the sibling add_text_overlay, which reads like an overlapping operation.

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?

There is a genuine exclusion ("This edits project text, not spoken audio or captions"), which is real when-not guidance. But no alternative is named for the ambiguous case, and the obvious overlap with add_text_overlay is left unresolved, so the agent must infer which text tool to pick.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources