Skip to main content
Glama
Sign In
slidecold-mcp

slidecold-mcp

by slidecold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Delete (unsend) a message

delete_conversation_message
DestructiveIdempotent

Remove a conversation message locally and queue a best-effort Instagram unsend when possible.

Instructions

Delete (unsend) a message. Required API key scope: conversations:write. DELETE /conversations/{id}/messages/{messageId} Deletes the message locally and, when possible, queues a best-effort unsend on Instagram.

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": {
      "id": "<id>",
      "messageId": "<messageId>"
    },
    "name": "delete_conversation_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPath parameter `id`.
messageIdYesPath parameter `messageId`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description still adds non-obvious behavior: the delete is local, and the Instagram-side unsend is queued 'best-effort', meaning remote removal can silently fail — a critical trait an agent would not learn from annotations alone. It stops short of describing the return payload or what happens on partial failure.

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?

Four short lines: purpose first, then the auth requirement, then the route, then the behavioral caveat. No filler, and each line carries distinct information.

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?

For a two-parameter destructive tool with no output schema, the definition covers purpose, scope, route, and failure semantics. The remaining gap is that it never says what a call returns or how the caller learns whether the best-effort unsend succeeded.

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?

Schema coverage is 100%, but the schema descriptions are pure tautologies ('Path parameter `id`'), so they convey nothing. The endpoint template in the description is what actually disambiguates `id` as the conversation identifier and `messageId` as the message identifier, adding genuine meaning beyond the schema.

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?

States a specific verb and resource ('Delete (unsend) a message') and pins it down with the concrete endpoint DELETE /conversations/{id}/messages/{messageId}. An agent can distinguish it from siblings like send_conversation_reply or update_conversation without inspecting any schema.

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 supplies a hard prerequisite ('Required API key scope: conversations:write'), which is real usage guidance, but it never states when to choose this over alternatives or what preconditions must hold (e.g., whether the message must belong to the caller). Usage is implied by the endpoint rather than explained.

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