Skip to main content
Glama

title_update

Modify the text, font, size, color, style, position, or inputs of an existing Text+ title, including titles inside MCP compound clips.

Instructions

Change text/style of an existing Text+ title (also inside MCP compound titles). See title_add for fields.

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": "<clip>"
    },
    "name": "title_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipYes
fontNo
sizeNo
textNo
colorNo
styleNo
inputsNo
positionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It mentions that the title may be inside an MCP compound title, but does not disclose mutation semantics, permission requirements, reversibility, or how omitted optional fields are treated.

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 definition is two short sentences with no wasted wording. The primary action and scope are front-loaded, followed by a useful pointer to title_add for field details.

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?

For an eight-parameter mutation tool with no annotations, no output schema, and zero schema description coverage, this description is too sparse. It gives a clear high-level purpose but omits parameter guidance and mutation-specific behavioral details needed to invoke the tool confidently.

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 0% and the description provides only partial field hints ('text/style'). It does not explain the roles of the required clip parameter or the other optional parameters such as font, size, color, inputs, or position, and merely refers agents to title_add for fields.

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 states a specific verb (change) and resource (existing Text+ title), including the supported edge case of MCP compound titles. It distinguishes update from creation by specifying an existing title, though it references title_add only for fields rather than explicitly routing creation there.

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 by 'existing' and the reference to title_add, suggesting this tool is for modifying existing titles rather than adding new ones. However, it does not explicitly state when not to use it or name alternatives for related operations such as clip-level updates.

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