Skip to main content
Glama

Caption styles and each place's margins

list_caption_styles
Read-onlyIdempotent

Lists caption styles with suited uses, options, and button margins in pixels per screen or frame, sourced and dated. Use it to pick a style and locations for caption_video or find where app buttons sit.

Instructions

Use it when the user wants the caption styles, or the margins an app's buttons leave free. Lists easycaptionkit's caption styles with what each suits, its options, and every place's margins, in pixels of the screen or frame they are for, each with its source and the day it was read. It reads no file and runs no browser or ffmpeg. Use it to pick a style and the places for caption_video, or to tell the user where an app's buttons sit. The captions playbook (makersmcp_playbook) has the whole job. (easycaptionkit 0.1.4, on this machine.)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_caption_styles"
  }
}

Input Schema

NameRequiredDescriptionDefault
wait_secondsNoHow long to wait for the result, counted from the start of the call, before returning a job_id to wait on. Some clients end a call after 60 or 240 seconds; 45 is safe in all of them.

Output Schema

NameRequiredDescriptionDefault
kitYes
docsNoThe notes the text shows, and where each one is.
nextNoWhat to do next, as the Next line says.
toolYes
filesNo
folderNoWhere the kit saved its files.
job_idYes
passedNoFor checks: whether the check passed.
statusYes
continuedNoTrue when this call continued the job of an identical call whose answer did not reach the client, instead of starting another.
exit_codeNo
last_lineNoWhat the kit was doing last.
expires_atNoWhen the download links stop working.
next_actionNo
elapsed_secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world and non-destructive behavior, so the bar is lower; the description still adds real context by stating that no file is read and no browser or ffmpeg is launched, and that each returned entry carries its source and the day it was read. The version/machine note ('easycaptionkit 0.1.4, on this machine') further anchors which environment's data is returned.

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?

Usage triggers are front-loaded and every sentence carries information about scope, payload or boundaries. It is slightly overstuffed and repetitive with two consecutive 'Use it...' clauses plus a nested parenthetical, which makes it denser than needed, but nothing is truly wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still summarizes what comes back (styles, options, per-place margins, source, read date), and it covers safety boundaries and downstream routing. For a zero-required-parameter listing tool, an agent has everything needed to call it and interpret the result.

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 100% and the single optional parameter (wait_seconds, with default, min/max and an explanation of client timeouts) is fully documented in the schema. The description adds nothing about it, which is acceptable but not value-adding — baseline 3 applies.

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?

States a specific verb and resource ('Lists easycaptionkit's caption styles') and enumerates the payload: styles with what each suits, their options, and per-place margins in pixels with source and read date. It also draws the boundary against caption_video (this picks the style; caption_video renders). An agent can distinguish it from siblings 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?

Gives explicit when-to-use triggers ('when the user wants the caption styles, or the margins an app's buttons leave free') and routes onward to caption_video for rendering and to makersmcp_playbook for the full workflow. It also declares boundaries ('reads no file and runs no browser or ffmpeg'), though there is no explicit when-not-to-use statement.

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