Skip to main content
Glama
Sign In
MEME

MEME

by renniyy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Delete a meme

delete_meme

Removes a meme you own by its ID; admins can remove any meme. Use to clean up or moderate meme content.

Instructions

Deletes a meme you own (admins may delete any).

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>"
    },
    "name": "delete_meme"
  }
}

Input Schema

NameRequiredDescriptionDefault
memeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the authorization model (owner-only, admin override) but says nothing about irreversibility, confirmation requirements, or what happens when the caller lacks permission on a destructive operation.

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?

A single short sentence with zero filler, and the authorization constraint is placed immediately after the action. Nothing could be trimmed without losing meaning.

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?

For a destructive, unannotated tool with no output schema, the definition is thin: it omits permanence, failure modes, and any note on the response. The ownership rule is the right instinct, but the implications of deletion remain undisclosed.

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 coverage is 0% and the single parameter memeId is never mentioned in the description. The parameter's meaning is largely self-evident from its name and required status, so this is a minor gap rather than a critical one, but the description adds no format or sourcing guidance for the ID.

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 gives a specific verb and resource ('Deletes a meme') plus a scope qualifier ('you own'). It is distinctive from siblings like edit_meme or report_content without needing to name them, though it doesn't explicitly contrast with any alternative action for memes you don't own.

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 ownership clause implies when this tool is applicable (your own memes, or any meme if admin), which is better than nothing. However, it does not point to what an agent should do instead for memes it doesn't own, such as report_content, leaving the routing decision to inference.

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

Deploy Server

Other Tools