MEME

Overview Schema Source Related Servers Discussions Admin

Edit meme texts and re-render

edit_meme

Updates caption text on a rendered meme and re-renders it, validating format slots and moderation while preserving the previous version in revision history.

Instructions

Edits the caption texts of a rendered meme and re-renders it. Texts are validated against format slots and re-moderated. The previous version is kept in the revision history.

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": {
      "memeId": "<memeId>",
      "texts": "<texts>"
    },
    "name": "edit_meme"
  }
}

Input Schema

Name	Required	Description	Default
`texts`	Yes
`title`	No
`memeId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavior: texts are validated against format slots, re-moderated, and the prior version persists in revision history (implying recoverability). It does not say what happens on slot mismatch or moderation rejection, nor whether authorization/ownership is required for the mutation.

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?

Three short sentences, front-loaded with the core action, with no filler. Each sentence adds a distinct fact (action, validation/moderation, history retention), though the definition is terse enough to leave gaps that a slightly longer treatment could have closed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations, no output schema, and a nested parameter object, the definition covers the essential mechanics but stops short of completeness. It does not describe the response (e.g., new revision identifier or rendered result), failure modes for slot validation or moderation, or the role of the 'title' parameter.

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

Parameters2/5

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

Schema description coverage is 0% for 3 parameters, including a nested free-form 'texts' object, so the description must compensate. 'Texts are validated against format slots' usefully hints that the object keys must match template slots, but 'title' is never mentioned and 'memeId' is left entirely to the schema, so two of three parameters remain semantically undocumented.

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?

States a specific verb and resource: 'Edits the caption texts of a rendered meme and re-renders it.' The phrase 'of a rendered meme' implicitly separates it from render_meme (which produces a new meme), but no sibling is named explicitly, so differentiation relies on inference.

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?

Usage is implied rather than stated: an agent can infer this is for changing captions on an existing meme rather than creating one. There is no explicit when-to-use vs. when-not guidance, no mention of prerequisites such as ownership or moderation state, and no pointer to render_meme for new memes.

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