Skip to main content
Glama
memebo-at

Memeboat MCP

Official
by memebo-at
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Create a meme

create_meme

Create shareable memes from 25,000+ templates by captioning them. Supports multiple captions, font, color, outline, and layout customization.

Instructions

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). Captions can be plain strings or objects with per-caption color/outline/font; optional global font and layout ("top" = captions in a white bar above the image). Returns the meme page URL and a direct image URL. Rate-limited per IP — space out repeated calls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fontNoDefault font for all captions, one of: impact, arial, helvetica, times, courier, titillium, thick, kalam, comic, notosans, notosanshebrew
styleNoAlternate background style name from get_meme_template's availableStyles, e.g. "maga"
textsYesCaptions, top-to-bottom. Each is a string or { text, color?, outline?, font? }. At least one must be non-empty.
layoutNolayout:"top" puts captions in a white bar above the image; "default" overlays them on the image
templateYesTemplate slug, e.g. "x-x-everywhere"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / font
      Added value: +{
+  "description": "Default font for all captions, one of: impact, arial, helvetica, times, courier, titillium, thick, kalam, comic, notosans, notosanshebrew",
+  "type": "string"
+}
    • 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\"",
+  "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? }. At least one must be non-empty."
    • addedInput schema / properties / texts / items / anyOf
      Added value: +[
+  {
+    "maxLength": 200,
+    "type": "string"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "color": {
+        "description": "Fill color: hex (#rgb/#rrggbb) or white/black/red/yellow/blue/green",
+        "type": "string"
+      },
+      "font": {
+        "description": "Font for this caption, one of: impact, arial, helvetica, times, courier, titillium, thick, kalam, comic, notosans, notosanshebrew",
+        "type": "string"
+      },
+      "outline": {
+        "description": "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"
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavior: caption order logic, optional styling, layout options, and return values (meme page URL and direct image URL). Also notes rate limiting per IP.

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?

Single paragraph with no redundancy. Front-loaded with purpose, each sentence adds essential information. Efficient and well-structured.

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?

For a 5-parameter tool with no output schema, the description adequately explains parameter behavior, return values, and constraints (rate limiting). No gaps identified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds significant value beyond schema by explaining caption ordering rules and layout behavior ('top' puts captions in a white bar). Provides context not in schema.

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?

The description clearly states the verb ('create'), resource ('real, shareable meme'), and platform ('memebo.at'). It distinguishes from siblings by focusing on creation rather than retrieval or search.

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?

Describes caption placement rules and mentions rate limiting ('space out repeated calls'), but does not explicitly state when to use this tool versus siblings like get_meme_template or search_meme_templates.

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