Skip to main content
Glama

delete_note

Remove a specific note from HackMD by providing its unique note ID using the MCP server's functionality.

Instructions

Delete a note

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteIdYesNote ID

Implementation Reference

  • The handler function that executes the delete_note tool. It calls client.deleteNote(noteId) and formats a success or error response.
    async ({ noteId }) => {
      try {
        const result = await client.deleteNote(noteId);
        return {
          content: [
            {
              type: "text",
              text: `Note ${noteId} deleted successfully:\n${JSON.stringify(result, null, 2)}`,
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [{ type: "text", text: `Error: ${error.message}` }],
          isError: true,
        };
      }
    },
  • Zod input schema for the delete_note tool, requiring a noteId string parameter.
    {
      noteId: z.string().describe("Note ID"),
    },
  • Full registration of the delete_note tool using server.tool(), including name, description, schema, hints, and inline handler.
    server.tool(
      "delete_note",
      "Delete a note",
      {
        noteId: z.string().describe("Note ID"),
      },
      {
        title: "Delete a note",
        readOnlyHint: false,
        destructiveHint: true,
        idempotentHint: true,
        openWorldHint: true,
      },
      async ({ noteId }) => {
        try {
          const result = await client.deleteNote(noteId);
          return {
            content: [
              {
                type: "text",
                text: `Note ${noteId} deleted successfully:\n${JSON.stringify(result, null, 2)}`,
              },
            ],
          };
        } catch (error: any) {
          return {
            content: [{ type: "text", text: `Error: ${error.message}` }],
            isError: true,
          };
        }
      },
    );
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Delete a note' which implies a destructive mutation, but doesn't disclose behavioral traits like whether deletion is permanent, requires specific permissions, has side effects, or returns confirmation. This is a significant gap for a mutation tool with zero annotation coverage.

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?

The description is extremely concise with just three words, front-loaded and zero waste. It efficiently communicates the core action without unnecessary elaboration, making it easy to parse quickly.

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 the tool's complexity (a destructive mutation), lack of annotations, and no output schema, the description is incomplete. It fails to address critical aspects like return values, error conditions, or behavioral nuances, leaving the agent with insufficient information for reliable use.

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?

The input schema has 1 parameter with 100% description coverage ('Note ID'), so the schema fully documents it. The description doesn't add any parameter details beyond what the schema provides, but with 0 parameters needing extra explanation, a baseline of 4 is appropriate as no compensation is required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Delete a note' clearly states the action (delete) and resource (note), but it's vague about scope and doesn't distinguish from sibling tools like delete_team_note. It provides basic purpose but lacks specificity about what kind of note it deletes (e.g., personal vs. team).

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 is provided on when to use this tool versus alternatives like delete_team_note or update_note. The description doesn't mention prerequisites, such as needing an existing note ID, or exclusions, leaving the agent to infer usage from context alone.

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

Related 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/yuna0x0/hackmd-mcp'

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