MEME

Overview Schema Source Related Servers Discussions Admin

Edit a template

edit_template

Customize a meme template by updating its name, hex color palette, or default texts; built-in templates can be modified though not deleted.

Instructions

Edit a template's name, palette (hex colors) or default texts. Built-in templates cannot be deleted but can be customized.

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": {
      "templateId": "<templateId>"
    },
    "name": "edit_template"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`palette`	No
`defaults`	No
`templateId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

B3/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It states that built-in templates are editable, but omits critical mutation semantics: whether omitted fields are preserved or reset, whether palette must be supplied in full, permission requirements, and error behavior for built-in versus custom templates. The mention of deletion is also tangential for an edit tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the editable fields front-loaded, so it is efficiently sized. However, the second sentence is partly wasted on deletion, which this tool cannot do, diluting focus on edit-specific behavior.

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

Completeness2/5

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

A mutation tool with a nested palette object, no annotations, no output schema, and zero schema description coverage needs more than two sentences. Missing are partial-update semantics, palette completeness requirements, and the success/failure outcome an agent should expect.

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

Parameters3/5

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

Schema description coverage is 0% with four parameters, so the description must compensate. It usefully clarifies that palette values are hex colors and that 'defaults' holds default texts, mapping to three of the four fields, but it says nothing about the four required palette keys (bg/panel/accent/text), the 200-character cap on default values, or that templateId is the sole required identifier.

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 names a specific verb ('Edit') and resource ('template') and enumerates the editable surfaces: name, palette, and default texts. It is clearly distinguishable from list_templates and the meme-rendering siblings, though it does not explicitly reference any sibling.

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 only implied: an agent infers it should call this when it needs to change an existing template. The note that built-in templates 'can be customized' gives a useful boundary, but there is no explicit when-to-use/when-not-to-use guidance and no advice on preferring edit_template over, say, generate_meme for customization.

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