Skip to main content
Glama

generate-meme

Select a template from 211 built-in memes and add your text to generate a custom image. Returns a PNG URL and markdown for embedding.

Instructions

Generates a meme image from 211 built-in templates. Returns a direct PNG URL and embed-ready markdown. Input: template ID (default: drake), top line, optional bottom line, optional middle line (for 3-line templates like panik-kalm-panik). Popular templates: drake, buzz (X Everywhere), fry, fine (This Is Fine), success, panik-kalm-panik, boat (I Should Buy a Boat), aag (Ancient Aliens), blb (Bad Luck Brian). $0.005/call — free upstream, no API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
templateNoMeme template ID. Popular options: drake, buzz, fry, fine, success, panik-kalm-panik, boat, aag, bad, blb, yuno. Call /cap/list-templates (free) for the full 211. Default: drake.
topNoTop / first line text. Required.
bottomNoBottom / second line text. Optional.
middleNoMiddle / third line text. Only used if the template has 3+ lines (e.g. panik-kalm-panik). Ignored otherwise.
widthNoOutput image width in pixels (100–800). Default 600.
Behavior4/5

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

Despite no annotations, the description discloses the output format, optional parameters, default template, and cost. It does not mention rate limits or error handling for invalid template IDs, but overall it provides good behavioral context.

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?

The description is a single paragraph that efficiently conveys key information without wasted words. It includes cost and input details, though it could be slightly more structured for readability.

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?

Given the number of parameters and lack of output schema, the description provides sufficient context: default, popular templates, optional fields, cost, and output format. It lacks guidance on invalid template IDs and doesn't address the sibling tool overlap, but is generally complete.

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?

The schema covers all five parameters with descriptions, and the description adds extra value by listing popular templates, explaining the default, and clarifying how the 'middle' parameter is used for 3-line templates.

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 clearly states the tool generates a meme image from 211 built-in templates and returns a PNG URL and markdown. However, it does not differentiate from the sibling 'meme-generator', which could cause confusion.

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 mentions popular templates and how to get the full list, but does not provide explicit guidance on when to use this tool versus alternatives like 'meme-generator'. It includes cost info, which is helpful but does not substitute for clear usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thebrierfox/the-stall'

If you have feedback or need assistance with the MCP directory API, please join our Discord server