Skip to main content
Glama

github_activity_get_thread_subscription_for_authenticated_user

Retrieve the subscription status of a specific notification thread for the authenticated GitHub user.

Instructions

Get a thread subscription for the authenticated user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thread_idYesthread_id

Implementation Reference

  • Handler function for 'github_activity_get_thread_subscription_for_authenticated_user'. Makes a GET request to /notifications/threads/{thread_id}/subscription to retrieve the authenticated user's subscription for a specific thread.
    name: "github_activity_get_thread_subscription_for_authenticated_user",
    description: "Get a thread subscription for the authenticated user",
    inputSchema: z.object({
      thread_id: z.string().describe("thread_id")
    }),
    handler: async (args: Record<string, any>) => {
      return githubRequest("GET", `/notifications/threads/${args.thread_id}/subscription`, undefined, undefined);
    },
  • Input schema for the tool: requires a thread_id string parameter.
    inputSchema: z.object({
      thread_id: z.string().describe("thread_id")
    }),
  • src/index.ts:108-110 (registration)
    General tool registration loop: all tools (including this one) are registered with the MCP server via server.tool() using their name, description, schema, and handler.
      .flatMap((m) => m.tools);
    
    for (const tool of allTools) {
  • src/index.ts:55-57 (registration)
    The activityTools array (containing this tool) is included in the allToolModules list, making it available for registration under the 'activity' category.
    const allToolModules = [
      { category: "actions", tools: actionsTools },
      { category: "activity", tools: activityTools },
  • The githubRequest helper function used by the handler to make HTTP requests 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(() => "");
Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. It indicates a read operation ('Get'), which matches the tool's nature. However, it does not disclose any side effects, permission requirements, or expected output beyond the name.

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

Conciseness3/5

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

The description is a single short sentence, making it concise. However, it is too minimal to convey useful information beyond the tool's name, scoring average on structuring content.

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

Completeness3/5

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

Given the simple input and no output schema, the description is minimally complete for a basic getter. However, it lacks details on authentication requirements and return value format, leaving room for improvement.

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

Parameters1/5

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

The input schema has one parameter 'thread_id' with a tautological description 'thread_id'. The tool description does not add any extra meaning or context about this parameter, failing to compensate for the schema's lack of useful information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action 'Get' and the resource 'thread subscription for the authenticated user', which is specific and distinguishes it from sibling tools like 'set_thread_subscription' and 'delete_thread_subscription'.

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, such as when to get vs set or delete a subscription. It lacks any context about prerequisites 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