Skip to main content
Glama

github_activity_set_thread_subscription

Subscribe or unsubscribe to a GitHub thread (issue or pull request) to manage email notifications for that conversation.

Instructions

Set a thread subscription

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thread_idYesthread_id
bodyNoRequest body (JSON object)

Implementation Reference

  • The handler function for the 'github_activity_set_thread_subscription' tool. It sends a PUT request to `/notifications/threads/{thread_id}/subscription` with an optional request body. This sets the authenticated user's subscription to a thread (ignored, subscribed, etc.).
    {
      name: "github_activity_set_thread_subscription",
      description: "Set a thread subscription",
      inputSchema: z.object({
        thread_id: z.string().describe("thread_id"),
        body: z.record(z.string(), z.unknown()).optional().describe("Request body (JSON object)")
      }),
      handler: async (args: Record<string, any>) => {
        return githubRequest("PUT", `/notifications/threads/${args.thread_id}/subscription`, args.body, undefined);
      },
  • The input schema (Zod) for the tool, defining: thread_id (required string) and body (optional record).
    inputSchema: z.object({
      thread_id: z.string().describe("thread_id"),
      body: z.record(z.string(), z.unknown()).optional().describe("Request body (JSON object)")
    }),
  • src/index.ts:110-129 (registration)
    The tool is registered via server.tool() in the MCP server loop. All tools from activityTools array are iterated and registered by name, description, inputSchema, and handler.
    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) {
            const message = err instanceof Error ? err.message : String(err);
            return {
              content: [{ type: "text" as const, text: `Error: ${message}` }],
              isError: true,
            };
          }
        }
      );
  • src/tools/index.ts:2-3 (registration)
    The activityTools array is re-exported from the tools index barrel file, so it can be imported by src/index.ts.
    export { actionsTools } from "./actions.js";
    export { activityTools } from "./activity.js";
  • The githubRequest helper function used by the handler to make authenticated HTTP requests to the GitHub REST 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>;
    }
Behavior1/5

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

With no annotations, the description must disclose behavioral traits. It fails to mention authentication needs, side effects, idempotency, or what setting a subscription entails.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief but lacks substantive content. It does not earn its place as it omits critical details, making it under-specified rather than efficiently concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of annotations and output schema, the description should provide sufficient context. It fails to describe the effect of the operation, the role of the body parameter, or any related constraints.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has descriptions that are trivial (e.g., 'thread_id' repeated). The description adds no meaning beyond what the schema provides; it does not explain the body structure or expected values.

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 'Set a thread subscription' clearly identifies the action and resource. It is straightforward, but it does not differentiate from sibling tools like 'delete_thread_subscription' or 'get_thread_subscription_for_authenticated_user'.

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. There is no mention of prerequisites, context, or exclusions.

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