Skip to main content
Glama

update_team_note

Modify team notes in HackMD by updating content, permissions, or custom permalinks using the specified note ID and team path. Simplifies collaborative note management.

Instructions

Update an existing note in a team

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteIdYesNote ID
optionsYesUpdate note options
teamPathYesTeam path

Implementation Reference

  • The handler function for the 'update_team_note' tool. It takes teamPath, noteId, and options, calls client.updateTeamNote, and returns a formatted success message or error.
    async ({ teamPath, noteId, options }) => {
      try {
        const result = await client.updateTeamNote(teamPath, noteId, options);
        return {
          content: [
            {
              type: "text",
              text: `Team note ${noteId} updated successfully:\n${JSON.stringify(result, null, 2)}`,
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [{ type: "text", text: `Error: ${error.message}` }],
          isError: true,
        };
      }
    },
  • Registers the 'update_team_note' tool on the MCP server, specifying name, description, input schema, and metadata hints.
    server.tool(
      "update_team_note",
      "Update an existing note in a team",
      {
        teamPath: z.string().describe("Team path"),
        noteId: z.string().describe("Note ID"),
        options: UpdateNoteOptionsSchema.describe("Update note options"),
      },
      {
        title: "Update a note in a Team's workspace",
        readOnlyHint: false,
        destructiveHint: true,
        idempotentHint: false,
        openWorldHint: true,
      },
  • Zod schema defining the 'options' parameter for the update_team_note tool, including content, permissions, and permalink.
    export const UpdateNoteOptionsSchema = z.object({
      content: z.string().optional().describe("New note content"),
      readPermission: z
        .enum([
          NotePermissionRole.OWNER,
          NotePermissionRole.SIGNED_IN,
          NotePermissionRole.GUEST,
        ])
        .optional()
        .describe("Read permission"),
      writePermission: z
        .enum([
          NotePermissionRole.OWNER,
          NotePermissionRole.SIGNED_IN,
          NotePermissionRole.GUEST,
        ])
        .optional()
        .describe("Write permission"),
      permalink: z.string().optional().describe("Custom permalink"),
    });
  • tools/index.ts:20-20 (registration)
    Calls registerTeamNotesApiTools which includes the registration of update_team_note, as part of registering all tools.
    registerTeamNotesApiTools(server, client);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Update' implies a mutation operation, the description doesn't specify what happens on success/failure, whether changes are reversible, what permissions are required, or any rate limits. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 that states the core functionality without any wasted words. It's appropriately sized for a straightforward update operation and gets directly to the point.

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 this is a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what the tool returns, what error conditions might occur, or any behavioral nuances. The agent lacks critical information needed to properly invoke and handle responses from this tool.

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 the schema already documents all three parameters thoroughly. The description adds no additional parameter information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 clearly states the action ('Update') and resource ('an existing note in a team'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'update_note' (which likely updates notes in a different context), leaving some ambiguity about when to use one versus the other.

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. With sibling tools like 'update_note' and 'create_team_note' available, there's no indication of prerequisites, appropriate contexts, or distinctions between these similar operations. The agent must infer usage from the name 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