Skip to main content
Glama

meme-generator

Generate meme image URLs from text with top and bottom lines. Choose from 211 templates or let the tool auto-select based on a topic keyword.

Instructions

Generate a meme image URL from text. Provide text_top and text_bottom (the two lines of the meme), and optionally a template name. If no template is given, supply a topic keyword and a fitting template will be chosen automatically. Returns a direct image URL you can embed in messages, posts, or web pages. 211 templates available including drake, doge, distracted, buzz, fry, success, gru, oprah, and more. Free upstream: memegen.link (no API key, unlimited requests). Common agent use cases: social media content generation, reaction images, marketing copy, presentation humor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
text_topNoTop line of the meme (the setup or rejected option). Max 120 chars.
text_bottomNoBottom line of the meme (the punchline or preferred option). Max 120 chars.
templateNoMeme template ID. Examples: drake, doge, distracted, buzz, fry, gru, success, oprah, astronaut, brain, fine, picard. Omit to auto-select from topic.
topicNoTopic keyword used to auto-select a template when 'template' is omitted. Examples: 'choice', 'crypto', 'success', 'fire', 'ai'. Ignored if template is specified.
styleNoOptional style variant (e.g. 'animated', 'dark', 'no'). Only supported by some templates. Defaults to template default.
widthNoOutput image width in pixels. Defaults to 600.
heightNoOutput image height in pixels. Defaults to 450.
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses non-destructive behavior (generates a URL), free upstream (no API key, unlimited requests), and number of templates (211). It does not mention potential errors or rate limits, but for a simple tool, transparency is high.

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?

Description is concise with no wasted words. It is structured logically: purpose, inputs, optional features, output format, template examples, use cases. Every sentence serves a purpose.

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 7 parameters and no output schema, the description covers all aspects: parameter roles, output format (direct image URL), template examples, auto-selection feature, and use cases. It is sufficiently complete for agents to invoke the tool correctly.

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 the role of each parameter (e.g., 'the two lines of the meme', 'auto-select from topic', 'only supported by some templates'). This helps agents understand parameter semantics beyond the schema descriptions.

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?

Description clearly states the tool generates a meme image URL from text, specifying inputs (text_top, text_bottom, optional template or topic) and output (direct image URL). It mentions common use cases like social media content and reaction images, distinguishing it from sibling tools.

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?

Description explains when to use (e.g., social media content, reaction images) and how to choose between providing a template or topic for auto-selection. While it doesn't explicitly state when not to use or list alternatives, it provides adequate guidance for typical agent use cases.

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