Skip to main content
Glama

delete_team_note

Remove a note from a HackMD team by providing the team path and note ID.

Instructions

Delete a team note

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
team_pathYesTeam path
note_idYesNote ID

Implementation Reference

  • Handler for 'delete_team_note' tool: accepts team_path and note_id, sends a DELETE request to /teams/{team_path}/notes/{note_id} via hackmdFetch, and returns success or error.
    server.tool(
      "delete_team_note",
      "Delete a team note",
      {
        team_path: z.string().min(1).describe("Team path"),
        note_id: z.string().min(1).describe("Note ID"),
      },
      async ({ team_path, note_id }) => {
        try {
          return success(
            await hackmdFetch(`/teams/${team_path}/notes/${note_id}`, { method: "DELETE" })
          );
        } catch (e) {
          return error((e as Error).message);
        }
      }
    );
  • src/tools.ts:231-247 (registration)
    Registration of 'delete_team_note' tool on the MCP server with Zod schema validation (team_path and note_id as required strings). The tool is registered alongside other team note CRUD operations.
    server.tool(
      "delete_team_note",
      "Delete a team note",
      {
        team_path: z.string().min(1).describe("Team path"),
        note_id: z.string().min(1).describe("Note ID"),
      },
      async ({ team_path, note_id }) => {
        try {
          return success(
            await hackmdFetch(`/teams/${team_path}/notes/${note_id}`, { method: "DELETE" })
          );
        } catch (e) {
          return error((e as Error).message);
        }
      }
    );
  • Imports: hackmdFetch from './api.js' handles the actual HTTP requests; success and error from './helpers.js' format MCP tool responses.
    import { z } from "zod";
    import type { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
    import { hackmdFetch } from "./api.js";
    import { success, error } from "./helpers.js";
Behavior2/5

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

No annotations provided, and description fails to disclose behavioral traits such as irreversibility, authorization needs, or error conditions. The word 'Delete' implies destructiveness but gives no further detail.

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?

Single sentence is efficient, but lacks any additional structure or breaking points. Could be slightly more informative without losing conciseness.

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?

Given no output schema and two parameters, the description does not explain return value, success/failure signals, or relationship to sibling tools. Incomplete for a destructive operation.

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 100%, so description adds no extra value beyond the schema's minimal param descriptions ('Team path', 'Note ID'). Baseline score of 3 is appropriate.

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?

Description clearly states the action (delete) and resource (team note), but does not distinguish from sibling 'delete_note' which deletes a personal note. Lacks specificity about scope.

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?

No guidance on when to use this tool versus alternatives like 'delete_note' or 'update_team_note'. No prerequisites or context provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zyx1121/hackmd-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server