Skip to main content
Glama

github_agent_tasks_get_task_by_repo_and_id

Retrieve a GitHub task's details using its repository owner, repo name, and task ID. This tool returns the task's current information.

Instructions

Get a task by repo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesowner
repoYesrepo
task_idYestask_id

Implementation Reference

  • Handler function for github_agent_tasks_get_task_by_repo_and_id: performs a GET request to `/agents/repos/{owner}/{repo}/tasks/{task_id}` using the githubRequest helper.
    handler: async (args: Record<string, any>) => {
      return githubRequest("GET", `/agents/repos/${args.owner}/${args.repo}/tasks/${args.task_id}`, undefined, undefined);
    },
  • Input schema for the tool: requires owner (string), repo (string), and task_id (string).
    inputSchema: z.object({
      owner: z.string().describe("owner"),
      repo: z.string().describe("repo"),
      task_id: z.string().describe("task_id")
    }),
  • Tool definition registered in the agentTasksTools array with name 'github_agent_tasks_get_task_by_repo_and_id'.
    {
      name: "github_agent_tasks_get_task_by_repo_and_id",
      description: "Get a task by repo",
      inputSchema: z.object({
        owner: z.string().describe("owner"),
        repo: z.string().describe("repo"),
        task_id: z.string().describe("task_id")
      }),
      handler: async (args: Record<string, any>) => {
        return githubRequest("GET", `/agents/repos/${args.owner}/${args.repo}/tasks/${args.task_id}`, undefined, undefined);
      },
    },
  • src/index.ts:110-130 (registration)
    Registration loop in src/index.ts that iterates all tools (including agent-tasks) and registers them with the MCP server.
    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,
            };
          }
        }
      );
    }
  • 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(() => "");
        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 are provided, and the description does not disclose behavioral traits such as read-only nature, side effects, or authentication requirements. The description is insufficient to inform an agent about safety or expected behavior.

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 sentence, which is concise but too brief to convey useful information. It could be expanded to include more details without becoming unnecessarily verbose.

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?

No output schema is provided, and the description does not explain what the response contains. For a retrieval tool, this is a notable gap, but the tool is simple enough that the basic purpose is somewhat clear.

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?

Input schema has 100% description coverage, but the descriptions are merely field names ('owner', 'repo', 'task_id'), adding no extra meaning. The tool description does not elaborate on parameter semantics either.

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 states 'Get a task by repo', which implies retrieving a specific task. However, it does not mention that the task_id is required, making it slightly vague compared to the tool name which includes 'by_repo_and_id'. It does distinguish from siblings like 'get_task_by_id' and list tools, but not explicitly.

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 such as 'github_agent_tasks_get_task_by_id' or 'github_agent_tasks_list_tasks_for_repo'. The description provides no context for selection.

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