Skip to main content
Glama
mcollina

GitHub Notifications MCP Server

mark-thread-done

Mark a GitHub notification thread as completed to clear it from your notifications list and manage your GitHub inbox efficiently.

Instructions

Mark a GitHub notification thread as done

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thread_idYesThe ID of the notification thread to mark as done

Implementation Reference

  • The handler function that executes the tool logic: deletes the notification thread via GitHub API and returns success or formatted error response.
    export async function markThreadDoneHandler(args: z.infer<typeof markThreadDoneSchema>) {
      try {
        // Make request to GitHub API
        await githubDelete(`/notifications/threads/${args.thread_id}`);
    
        return {
          content: [{
            type: "text",
            text: `Successfully marked thread ${args.thread_id} as done.`
          }]
        };
      } catch (error) {
        return {
          isError: true,
          content: [{
            type: "text",
            text: formatError(`Failed to mark thread ${args.thread_id} as done`, error)
          }]
        };
      }
    }
  • Zod schema defining the input parameter: thread_id (string).
    export const markThreadDoneSchema = z.object({
      thread_id: z.string().describe("The ID of the notification thread to mark as done")
    });
  • Registration function that calls server.tool() to register the 'mark-thread-done' tool with its name, description, schema, and handler.
    export function registerMarkThreadDoneTool(server: any) {
      server.tool(
        "mark-thread-done",
        "Mark a GitHub notification thread as done",
        markThreadDoneSchema.shape,
        markThreadDoneHandler
      );
    }
  • src/server.ts:42-42 (registration)
    Invocation of the tool registration function during server startup.
    registerMarkThreadDoneTool(server);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'mark as done' implies a state change, the description doesn't clarify what 'done' means operationally (does it archive, hide, or permanently remove the thread?), whether this requires specific permissions, or what happens after marking. This leaves significant behavioral questions unanswered.

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 communicates the core purpose without any wasted words. It's appropriately sized for a simple single-parameter tool and gets straight 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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'done' means operationally, what the expected outcome is, or how this differs from similar sibling operations. Given the context of multiple notification management tools, more guidance is needed.

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 the single parameter 'thread_id' clearly documented in the schema. The description adds no additional parameter information beyond what's already in the structured schema, so it meets the baseline expectation without adding extra value.

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 ('mark as done') and resource ('GitHub notification thread'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'mark-thread-read' or 'mark-notifications-read', which serve similar notification management functions.

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 multiple sibling tools for managing notifications (mark-thread-read, mark-notifications-read, mark-repo-notifications-read), there's no indication of what 'done' means compared to 'read' or when this specific operation is appropriate.

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/mcollina/mcp-github-notifications'

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