Skip to main content
Glama

Memeoki

Make memes

make_meme
Read-only

Turn a sentence into finished memes. Memeoki picks classic, well-known templates (Drake, Distracted Boyfriend, This Is Fine and 1800+ more) that fit the situation and writes fresh captions in the right format. Use it whenever someone asks for a meme, a reaction image or a funny way to say something. Returns PNG links ready to post or embed, plus the top meme as an inline preview image. Takes about 10 to 20 seconds. Show image_url to the person as an image. Every image carries a small memeoki.com mark: keep it. Examples: "when the standup runs 45 minutes", "my cat knocked my coffee off the desk", "cuando es lunes otra vez" (lang "es").

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": {
      "prompt": "<prompt>"
    },
    "name": "make_meme"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoCaption language code. One of: en, es, pt, fr, de, it, nl, pl, tr, ru, uk, ar, he, hi, bn, id, vi, th, ja, ko, zhen
toneNoOptional style: weirder (absurd), wholesome (kind), roast (playful teasing)
countNoHow many different memes to make (each on a different template)
promptYesThe situation or joke in plain words, e.g. "when the build passes on the first try". Specific beats generic.
previewNoInclude the top meme as an inline image so you can see it. Set false to get links only.
templateNoOptional template id to force one format (find ids with search_templates)

Output Schema

NameRequiredDescriptionDefault
memesYes
creditNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (which only declare it is a safe non-destructive read), the description discloses 10-20 second latency, that results are PNG links plus an inline preview, and a mandatory memeoki.com watermark that must be preserved. It also instructs the agent to render image_url as an image, which materially changes how output should be presented.

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?

Purpose, usage trigger, output, timing, and constraint are front-loaded in that order with no wasted framing. There is mild redundancy between the inline-preview sentence and the preview parameter, plus three examples where two would suffice, but nothing is confusing.

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?

With an output schema and annotations already covering safety, this description supplies the remaining agent-relevant facts: latency, attribution requirement, presentation instruction, and a delegate-to-search_templates path. Nothing needed to invoke it correctly is missing.

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

Parameters4/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 all six parameters and a baseline of 3 applies. The description adds real value by pairing a non-English example with lang "es" and by pointing to search_templates for template ids, going slightly beyond restating the 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?

"Turn a sentence into finished memes" gives a concrete verb and output, then names Memeoki's template selection and caption-writing behavior. It is clearly distinguishable from siblings caption_template (caption only) and search_templates (id lookup), which it even references for the template parameter.

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?

"Use it whenever someone asks for a meme, a reaction image or a funny way to say something" is an explicit trigger condition, and the template note routes the agent to search_templates when a specific format is wanted. There is no when-not-use guidance, but the positive routing is strong enough for a 4.

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.

Resources