Skip to main content
Glama

subtitle_style_set

Set a single subtitle appearance property such as scale, position, color, border size, or bold weight; returns the updated full style.

Instructions

Set one subtitle appearance property. Returns the full style after the change.

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": {
      "name": "<name>",
      "value": "<value>"
    },
    "name": "subtitle_style_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
valueYesscale: 0.1-10 · pos: 0-150 (100 = bottom) · color: #RRGGBBAA · border_size: 0-20 · bold: boolean

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load. It usefully discloses the return semantics ("Returns the full style after the change"), which partially substitutes for the missing output schema. It says nothing about persistence of the change, whether it applies to the currently selected subtitle or globally, or what happens on out-of-range values.

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 short sentences, the mutation and its scope front-loaded, the return behavior second. No filler and nothing buried.

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?

For a two-parameter write tool with no output schema, the description covers the core contract and return shape. It leaves out persistence scope, prerequisites, and error behavior, which an agent would need before mutating style state in a live session.

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 50%, and the value parameter already carries a per-property range description inside the schema. The description adds little beyond confirming that exactly one property is set per call, relying on the enum and the schema's inline range notes for the rest.

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?

"Set one subtitle appearance property" gives a specific verb plus a scoped resource, and the singular "one" explains why the calls take a name/value pair rather than a style object. It is clearly the write counterpart to subtitle_style_get, though that sibling is never named, so differentiation rests on inference from the tool name.

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?

The phrase "one subtitle appearance property" implies the granularity model: multiple changes require multiple calls. However there is no explicit statement of when to prefer this over related style tools, no mention of prerequisites such as a video or subtitle being loaded, and no 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