memeboat-mcp

Create a meme

create_meme

Create a real, shareable meme on memebo.at by captioning a template. texts are placed top-to-bottom: 1 caption = bottom text, 2 captions = classic top/bottom, N captions fill the template's boxes in order (match suggestedCaptionCount when possible). Returns the meme page URL and a direct image URL. Rate-limited per IP — space out repeated calls.

Input Schema

Name	Required	Description
`font`	No	Default font for all captions, one of: impact, arial, helvetica, times, courier, titillium, thick, kalam, comic, notosans, notosanshebrew
`style`	No	Alternate background style name from get_meme_template's availableStyles, e.g. 'maga'
`texts`	Yes	Captions, top-to-bottom. Each is a string or { text, color?, outline?, font? } for per-caption styling. At least one must be non-empty.
`layout`	No	layout:'top' puts captions in a white bar above the image; 'default' overlays them on the image
`template`	Yes	Template slug, e.g. "x-x-everywhere"

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 23, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

removedInput schema / properties / font / $ref

Removed value: -"#/properties/texts/items/anyOf/1/properties/font"

addedInput schema / properties / font / type
```
Added value: +"string"
```

changedInput schema / properties / texts / items / anyOf

Previous value: -[
-  {
-    "maxLength": 200,
-    "type": "string"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "color": {
-        "description": "Caption fill color: hex or white/black/red/yellow/blue/green",
-        "type": "string"
-      },
-      "font": {
-        "description": "Caption font, one of: impact, arial, helvetica, times, courier, titillium, thick, kalam, comic, notosans, notosanshebrew",
-        "type": "string"
-      },
-      "outline": {
-        "description": "Caption outline color; omit for an auto-picked readable outline",
-        "type": "string"
-      },
-      "text": {
-        "maxLength": 200,
-        "type": "string"
-      }
-    },
-    "required": [
-      "text"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "maxLength": 200,
+    "type": "string"
+  },
+  {
+    "properties": {
+      "color": {
+        "description": "Caption fill color: hex or white/black/red/yellow/blue/green",
+        "type": "string"
+      },
+      "font": {
+        "description": "Caption font, one of: impact, arial, helvetica, times, courier, titillium, thick, kalam, comic, notosans, notosanshebrew",
+        "type": "string"
+      },
+      "outline": {
+        "description": "Caption outline color; omit for an auto-picked readable outline",
+        "type": "string"
+      },
+      "text": {
+        "maxLength": 200,
+        "type": "string"
+      }
+    },
+    "required": [
+      "text"
+    ],
+    "type": "object"
+  }
+]

Changed7 schema fields changedJul 5, 2026

addedInput schema / properties / font

Added value: +{
+  "$ref": "#/properties/texts/items/anyOf/1/properties/font",
+  "description": "Default font for all captions, one of: impact, arial, helvetica, times, courier, titillium, thick, kalam, comic, notosans, notosanshebrew"
+}

addedInput schema / properties / layout

Added value: +{
+  "description": "layout:'top' puts captions in a white bar above the image; 'default' overlays them on the image",
+  "enum": [
+    "default",
+    "top"
+  ],
+  "type": "string"
+}

addedInput schema / properties / style

Added value: +{
+  "description": "Alternate background style name from get_meme_template's availableStyles, e.g. 'maga'",
+  "maxLength": 60,
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / properties / texts / description

Previous value: -"Caption strings, top-to-bottom. At least one must be non-empty."New value: +"Captions, top-to-bottom. Each is a string or { text, color?, outline?, font? } for per-caption styling. At least one must be non-empty."

addedInput schema / properties / texts / items / anyOf

Added value: +[
+  {
+    "maxLength": 200,
+    "type": "string"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "color": {
+        "description": "Caption fill color: hex or white/black/red/yellow/blue/green",
+        "type": "string"
+      },
+      "font": {
+        "description": "Caption font, one of: impact, arial, helvetica, times, courier, titillium, thick, kalam, comic, notosans, notosanshebrew",
+        "type": "string"
+      },
+      "outline": {
+        "description": "Caption outline color; omit for an auto-picked readable outline",
+        "type": "string"
+      },
+      "text": {
+        "maxLength": 200,
+        "type": "string"
+      }
+    },
+    "required": [
+      "text"
+    ],
+    "type": "object"
+  }
+]

removedInput schema / properties / texts / items / maxLength
```
Removed value: -200
```
removedInput schema / properties / texts / items / type
```
Removed value: -"string"
```

First observedJul 5, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full load and does reasonably well: it discloses the return artifacts (meme page URL plus direct image URL) and a per-IP rate limit with the mitigation of spacing calls. It does not say whether created memes are public/persistent or whether any auth or template availability constraints apply, which are the remaining behavioral gaps.

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?

Four sentences, each earning its place: purpose, caption-mapping rules, return values, rate limit. The core action is front-loaded in the first clause and nothing is padded or repeated from structured fields.

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?

For a create tool with no output schema, the description covers the essentials: what is produced, how the variable-length texts argument behaves, and the rate-limit constraint. It leaves out persistence/visibility and any prerequisite for obtaining a valid template slug, so it is strong but not exhaustive.

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%, so the schema already documents font, style, layout, template and per-caption styling, making 3 the baseline. The description does add genuine meaning the schema lacks — the positional semantics of texts (1 = bottom, 2 = top/bottom, N fills boxes in order) — which lifts it slightly, but the rest of the parameters are left entirely to the schema.

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 opens with a specific verb and resource ('Create a real, shareable meme ... by captioning a template') and states the output artifacts (page URL and image URL). It doesn't explicitly name the sibling template tools to distinguish itself, but the create-vs-read split against get_meme_template and search_meme_templates is unambiguous from the verb alone.

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?

It gives concrete guidance on how many captions to supply and how they map to the template's boxes, and tells the agent to match suggestedCaptionCount where possible. It also warns about rate limiting and spacing out repeated calls. It stops short of explicitly saying 'use search_meme_templates first to find a slug,' which is the one missing routing instruction.

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

All memeboat-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Create a meme

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources