Skip to main content
Glama

github_activity_mark_thread_as_done

Mark a GitHub notification thread as done, removing it from your active notifications.

Instructions

Mark a thread as done

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thread_idYesthread_id

Implementation Reference

  • The handler for github_activity_mark_thread_as_done: calls githubRequest with DELETE method on /notifications/threads/{thread_id}
    {
      name: "github_activity_mark_thread_as_done",
      description: "Mark a thread as done",
      inputSchema: z.object({
        thread_id: z.string().describe("thread_id")
      }),
      handler: async (args: Record<string, any>) => {
        return githubRequest("DELETE", `/notifications/threads/${args.thread_id}`, undefined, undefined);
      },
    },
  • Input schema for the tool: requires thread_id (string) as input
    {
      name: "github_activity_mark_thread_as_done",
      description: "Mark a thread as done",
      inputSchema: z.object({
        thread_id: z.string().describe("thread_id")
      }),
      handler: async (args: Record<string, any>) => {
        return githubRequest("DELETE", `/notifications/threads/${args.thread_id}`, undefined, undefined);
      },
    },
  • src/index.ts:110-121 (registration)
    Tools are registered via server.tool() in a loop that iterates over all tool modules, including activityTools which contains this tool
    for (const tool of allTools) {
      server.tool(
        tool.name,
        tool.description,
        tool.inputSchema.shape as any,
        async (args: any) => {
          try {
            const result = await tool.handler(args as any);
            return {
              content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }],
            };
          } catch (err) {
  • The tool is defined as part of the activityTools array exported from src/tools/activity.ts
    export const activityTools = [
  • The githubRequest helper function that executes the actual HTTP request to the GitHub API
    export async function githubRequest<T>(
      method: string,
      path: string,
      body?: Record<string, unknown>,
      params?: Record<string, string | number | boolean | string[] | undefined>
    ): Promise<T> {
      const url = new URL(`${BASE_URL}${path}`);
    
      if (params) {
        for (const [key, value] of Object.entries(params)) {
          if (value === undefined || value === null || value === "") continue;
          if (Array.isArray(value)) {
            url.searchParams.set(key, value.join(","));
          } else {
            url.searchParams.set(key, String(value));
          }
        }
      }
    
      const headers: Record<string, string> = {
        Authorization: `Bearer ${getToken()}`,
        Accept: "application/vnd.github+json",
        "X-GitHub-Api-Version": "2022-11-28",
        "User-Agent": "github-mcp/1.0.0",
      };
    
      if (body) {
        headers["Content-Type"] = "application/json";
      }
    
      const res = await fetch(url.toString(), {
        method,
        headers,
        body: body ? JSON.stringify(body) : undefined,
      });
    
      if (!res.ok) {
        const text = await res.text().catch(() => "");
        let detail = text;
        try {
          const json = JSON.parse(text);
          detail = json.message || text;
          if (json.errors) detail += ` -- ${JSON.stringify(json.errors)}`;
        } catch {}
        throw new Error(`GitHub API error ${res.status}: ${detail}`);
      }
    
      if (res.status === 204) return {} as T;
    
      return res.json() as Promise<T>;
    }
Behavior2/5

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

No annotations provided, so the description carries full burden. It only states the action without disclosing side effects, such as whether it also updates notifications or unsubscribes, or what 'done' means in terms of thread state.

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?

The description is a single, clear sentence. It is concise but could be slightly more informative (e.g., 'notification thread'). No wasted words.

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 only one parameter, the description is minimal. It lacks explanation of return value, error cases, or the effect of marking as done. For a simple action, more context would help an agent understand the consequences.

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 coverage is 100% with a description for thread_id. The description adds no additional meaning beyond the schema; it simply repeats the parameter name. Baseline 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?

The description clearly states the action ('Mark') and the resource ('a thread') with the state ('done'). It is specific but does not explicitly distinguish from siblings like 'mark_thread_as_read' or 'delete_thread_subscription', though the name helps.

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 marking as read or deleting a subscription. No context about typical use cases (e.g., dismissing a notification thread) or prerequisites.

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

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