Skip to main content
Glama

delete_team_note

Remove a note from a team's workspace by specifying the note ID and team path using the HackMD MCP Server integration. Simplify note management for collaborative projects.

Instructions

Delete a note in a team

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteIdYesNote ID
teamPathYesTeam path

Implementation Reference

  • The handler function that implements the core logic of the 'delete_team_note' tool. It calls client.deleteTeamNote(teamPath, noteId) and formats the response as MCP content.
      async ({ teamPath, noteId }) => {
        try {
          const result = await client.deleteTeamNote(teamPath, noteId);
          return {
            content: [
              {
                type: "text",
                text: `Team 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 defining the parameters for the delete_team_note tool: teamPath (string) and noteId (string).
    {
      teamPath: z.string().describe("Team path"),
      noteId: z.string().describe("Note ID"),
    },
  • Registration of the 'delete_team_note' tool using server.tool, including name, description, input schema, metadata hints, and handler reference.
        "delete_team_note",
        "Delete a note in a team",
        {
          teamPath: z.string().describe("Team path"),
          noteId: z.string().describe("Note ID"),
        },
        {
          title: "Delete a note in a Team's workspace",
          readOnlyHint: false,
          destructiveHint: true,
          idempotentHint: true,
          openWorldHint: true,
        },
        async ({ teamPath, noteId }) => {
          try {
            const result = await client.deleteTeamNote(teamPath, noteId);
            return {
              content: [
                {
                  type: "text",
                  text: `Team 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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool deletes a note but doesn't mention critical aspects like whether deletion is permanent, requires specific permissions, has side effects (e.g., affecting team history), or provides confirmation. This leaves significant gaps for 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?

The description is a single, efficient sentence with zero waste. It is front-loaded and appropriately sized for a simple tool, 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 destructive nature, no annotations, and no output schema, the description is incomplete. It fails to address behavioral risks (e.g., irreversible deletion), response expectations, or error handling, which are crucial for safe agent invocation.

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%, with both parameters ('noteId' and 'teamPath') documented in the schema. The description adds no additional meaning beyond the schema, such as format examples or relationships between parameters. Baseline 3 is appropriate as the schema handles parameter documentation.

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 'Delete a note in a team' clearly states the action (delete) and resource (note in a team), distinguishing it from sibling tools like 'delete_note' (which likely deletes a note without team context). However, it doesn't specify whether this is a permanent deletion or if notes can be restored, which slightly limits specificity.

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?

The description provides no guidance on when to use this tool versus alternatives like 'delete_note' or 'update_team_note'. It lacks context on prerequisites (e.g., needing the note ID and team path) or exclusions (e.g., not for deleting notes outside teams).

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