Skip to main content
Glama

Text Message Chat Maker

create_text_message_chat_maker
Read-onlyIdempotent

Prefill the Text Message Chat Maker: a text conversation that appears bubble by bubble, with typing dots and your own names. Returns a link that opens the Tool with these options; the user presses Export there to download the video. All options are optional. Icons and images that need a file upload are not supported.

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": "create_text_message_chat_maker"
  }
}

Input Schema

NameRequiredDescriptionDefault
bgNoBackground color around the chat screen. Default: "#00ff00".
fpsNoExport frame rate. Default: "30".
resNoExport resolution. Default: "720".
chatNoThe whole chat as one text: one line per message, each starting with "<" for a message from the left speaker or ">" for one from the right speaker, then the message text. For example "<Are you there?" then a new line and ">Yes". Default: "<Okay, don't freak out\n>That sentence always makes me freak out\n<I finally told my boss what I think of the new coffee machine\n>You did WHAT?\n<I said it tastes like a warm sock\n>And? What did she say?".
fontNoFont id of the text. Default: "inter".
leftNoName of the speaker on the left. It is the header's contact name and the label in their bubbles. Default: "Emma".
lookNoLight or dark chat screen. It also sets the screen and header colors; pass scolor and hcolor to change them. Default: "light".
paceNoHow fast the messages follow each other. Default: "normal".
sizeNoVideo size (aspect ratio) preset. Default: "16:9".
hnameNoShow the left speaker's name next to the avatar in the header. Default: true.
namesNoShow each speaker's name above their bubbles, once at the start of each run of messages from the same speaker. Default: true.
rightNoName of the speaker on the right. It is the label in their bubbles. Default: "Jake".
avatarNoShow the left speaker's round letter avatar in the header and beside their bubbles. Off by default. Default: false.
hcolorNoColor of the header bar. Overrides the color of the look. Default: "#f6f7f9".
headerNoShow the header with the left speaker's name (and avatar, when the avatar is on). Default: true.
lcolorNoBubble color of the speaker on the left. Default: "#e5e7eb".
rcolorNoBubble color of the speaker on the right. Also the avatar's color. Default: "#7c3aed".
scolorNoColor of the chat screen behind the bubbles. Overrides the color of the look. Default: "#ffffff".
typingNoShow typing dots before each message on the left. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: the call returns a link rather than a rendered video, export is a separate user action inside the Tool, and file-upload-based icons/images are unsupported. It stops short of stating link lifetime or expiry.

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, front-loaded with what the tool produces, followed by the export workflow and then the one hard limitation. Nothing is repeated from the name and every sentence carries information the agent needs.

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

Completeness4/5

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

With 19 optional parameters and no output schema, the description correctly supplies the missing piece by explaining that the return value is a link into the Tool. The unsupported-upload caveat covers the most likely failure case. Only minor operational details, such as anything about link persistence, are absent.

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 100% and every parameter carries its own description, default, and enum, so the schema does the heavy lifting. The description adds only the blanket note that all options are optional and the upload constraint, which does not add per-parameter meaning beyond the schema. Baseline 3 is appropriate.

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?

"Prefill the Text Message Chat Maker: a text conversation that appears bubble by bubble, with typing dots and your own names" gives a specific verb plus a concrete rendering of the resource, and it names the deliverable (a link into the Tool). It does not explicitly differentiate itself from the animation-generating siblings, which keeps it just below a 5.

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 description implies usage by explaining the workflow: call it to prefill options, then the user presses Export in the Tool to download the video. It gives no when-to-use guidance relative to the other creation tools and no explicit exclusions beyond the file-upload limitation, so usage is only implied.

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.