Skip to main content
Glama
Sign In
huly-mcp-selfhost

huly-mcp-selfhost

by JoKeks2023
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

delete_message

Destructive

Removes a chat message or thread reply by message ID from a specified workspace, helping clean up conversations and correct mistakes.

Instructions

Delete a message or thread reply

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": {
      "workspace": "<workspace>",
      "messageId": "<messageId>"
    },
    "name": "delete_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageIdYesMessage id (list_messages, list_comments, list_thread)
workspaceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.5.1

TDQS

C2.7/5.0
Behavior2/5

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

The destructiveHint=true annotation already signals this is a destructive operation, so the description's main remaining job is to explain consequences and it does not: nothing about irreversibility, permission requirements, or whether deleting a parent message removes its replies. The only added fact is that thread replies can be deleted too.

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?

A single short sentence with no filler and the core action front-loaded. Its brevity is appropriate but borders on under-specification rather than tightness.

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 write with two required params, no output schema, and a documented coverage gap on `workspace`, the description omits consequences, permissions, and parameter meaning, leaving an agent without what it needs to invoke this safely.

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?

At 50% schema coverage, the description must compensate, but it says nothing about parameters. The schema documents messageId (pointing to list_messages/list_comments/list_thread) but leaves the required `workspace` parameter entirely undescribed in both places.

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 ("Delete a message or thread reply") and clarifies that thread replies are included in scope, which distinguishes it from a bulk or thread-level deletion. It does not explicitly differentiate itself from close siblings such as delete_comment, but the resource is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to delete versus update or reply, no stated prerequisites (e.g., message ownership or admin permissions), and no indication of what happens to connected thread replies.

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