Skip to main content
Glama

list_repository_branches

Retrieve and display all branches from a specified repository on AtomGit, enabling users to view branch names and manage version control workflows.

Instructions

List branches in a repository

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesRepository owner, typically referred to as 'username'. Case-insensitive.
repoYesRepository name. Case-insensitive.
per_pageNoNumber of results per page
pageNoPage number

Implementation Reference

  • The main handler function that fetches the list of branches from the AtomGit API using atomGitRequest.
    export async function getBranchList(
      owner: string,
      repo: string,
      page?: number,
      per_page?: number
    ) {
    
      const query = new URLSearchParams();
      if (page) query.append("page", page.toString());
      if (per_page) query.append("per_page", per_page.toString());
    
      return atomGitRequest(
        `https://api.atomgit.com/repos/${encodeURIComponent(owner)}/${encodeURIComponent(repo)}/branches?${query.toString()}`,
        {
          method: "GET",
        }
      );
    }
  • Zod schema defining the input parameters for the list_repository_branches tool.
    export const ListBranchListSchema = z.object({
      owner: z.string().describe("Repository owner, typically referred to as 'username'. Case-insensitive."),
      repo: z.string().describe("Repository name. Case-insensitive."),
      per_page: z.number().describe("Number of results per page").optional(),
      page: z.number().describe("Page number").optional(),
    });
  • index.ts:162-166 (registration)
    Registration of the list_repository_branches tool in the ListTools handler.
    {
      name: "list_repository_branches",
      description: "List branches in a repository",
      inputSchema: zodToJsonSchema(branch.ListBranchListSchema),
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'List branches' implies a read-only operation, but the description doesn't mention pagination behavior (though parameters suggest it), rate limits, authentication requirements, or what the output format looks like. This leaves significant gaps for an agent to understand how to use it effectively.

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 states exactly what the tool does without any wasted words. It's appropriately sized for a straightforward listing operation and gets directly 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 tool with 4 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain the pagination behavior implied by the parameters, doesn't describe the return format, and provides no context about authentication or rate limits. The agent would need to guess about important operational aspects.

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?

With 100% schema description coverage, the input schema already fully documents all 4 parameters. The description adds no additional parameter context beyond what's in the schema, so it meets the baseline expectation but doesn't provide 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 ('List') and resource ('branches in a repository'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'get_repository_branch_details', which retrieves details about a specific branch rather than listing all branches.

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 siblings like 'get_repository_branch_details' and various issue/pull request tools, there's no indication of appropriate contexts, prerequisites, or exclusions for this listing operation.

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/kaiyuanxiaobing/atomgit-mcp-server'

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