Skip to main content
Glama
ddukbg

GitHub Enterprise MCP Server

list-branches

Retrieve branch information from GitHub Enterprise repositories to view, filter, and manage branches for development workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesUser or organization name
repoYesRepository name
protected_onlyNoWhether to show only protected branches
pageNoPage number
perPageNoItems per page

Implementation Reference

  • Main execution logic for list-branches tool: input validation, fetches branches via RepositoryAPI, formats using formatBranch, handles errors and empty results.
    }, async ({ owner, repo, protected_only, page, perPage }) => {
        try {
            // 매개변수 검증
            if (!owner || typeof owner !== 'string' || owner.trim() === '') {
                return {
                    content: [
                        {
                            type: "text",
                            text: "오류: 저장소 소유자(owner)는 필수 항목입니다."
                        }
                    ],
                    isError: true
                };
            }
            if (!repo || typeof repo !== 'string' || repo.trim() === '') {
                return {
                    content: [
                        {
                            type: "text",
                            text: "오류: 저장소 이름(repo)은 필수 항목입니다."
                        }
                    ],
                    isError: true
                };
            }
            const branches = await context.repository.listBranches(owner, repo, protected_only, page, perPage);
            // 브랜치가 없는 경우
            if (!branches || branches.length === 0) {
                return {
                    content: [
                        {
                            type: "text",
                            text: `저장소 '${owner}/${repo}'에 브랜치가 없습니다.`
                        }
                    ]
                };
            }
            // 브랜치 정보 형식화
            const formattedBranches = branches.map(formatBranch);
            return {
                content: [
                    {
                        type: "text",
                        text: `저장소 '${owner}/${repo}'의 브랜치 목록 (${branches.length}개)${protected_only ? ' (보호된 브랜치만)' : ''}:\n\n${JSON.stringify(formattedBranches, null, 2)}`
                    }
                ]
            };
        }
        catch (error) {
            console.error('브랜치 목록 조회 오류:', error);
            return {
                content: [
                    {
                        type: "text",
                        text: `브랜치 목록 조회 중 오류가 발생했습니다: ${error.message}`
                    }
                ],
                isError: true
            };
        }
  • Zod schema defining input parameters for the list-branches tool.
    owner: z.string().describe("저장소 소유자 (사용자 또는 조직)"),
    repo: z.string().describe("저장소 이름"),
    protected_only: z.boolean().default(false).describe("보호된 브랜치만 표시할지 여부"),
    page: z.number().default(1).describe("페이지 번호"),
    perPage: z.number().default(30).describe("페이지당 항목 수")
  • MCP server.tool registration for the list-branches tool, including schema and inline handler.
    server.tool("list-branches", {
        owner: z.string().describe("저장소 소유자 (사용자 또는 조직)"),
        repo: z.string().describe("저장소 이름"),
        protected_only: z.boolean().default(false).describe("보호된 브랜치만 표시할지 여부"),
        page: z.number().default(1).describe("페이지 번호"),
        perPage: z.number().default(30).describe("페이지당 항목 수")
    }, async ({ owner, repo, protected_only, page, perPage }) => {
        try {
            // 매개변수 검증
            if (!owner || typeof owner !== 'string' || owner.trim() === '') {
                return {
                    content: [
                        {
                            type: "text",
                            text: "오류: 저장소 소유자(owner)는 필수 항목입니다."
                        }
                    ],
                    isError: true
                };
            }
            if (!repo || typeof repo !== 'string' || repo.trim() === '') {
                return {
                    content: [
                        {
                            type: "text",
                            text: "오류: 저장소 이름(repo)은 필수 항목입니다."
                        }
                    ],
                    isError: true
                };
            }
            const branches = await context.repository.listBranches(owner, repo, protected_only, page, perPage);
            // 브랜치가 없는 경우
            if (!branches || branches.length === 0) {
                return {
                    content: [
                        {
                            type: "text",
                            text: `저장소 '${owner}/${repo}'에 브랜치가 없습니다.`
                        }
                    ]
                };
            }
            // 브랜치 정보 형식화
            const formattedBranches = branches.map(formatBranch);
            return {
                content: [
                    {
                        type: "text",
                        text: `저장소 '${owner}/${repo}'의 브랜치 목록 (${branches.length}개)${protected_only ? ' (보호된 브랜치만)' : ''}:\n\n${JSON.stringify(formattedBranches, null, 2)}`
                    }
                ]
            };
        }
        catch (error) {
            console.error('브랜치 목록 조회 오류:', error);
            return {
                content: [
                    {
                        type: "text",
                        text: `브랜치 목록 조회 중 오류가 발생했습니다: ${error.message}`
                    }
                ],
                isError: true
            };
        }
    });
  • Helper function to format branch objects for user-friendly output.
    function formatBranch(branch) {
        return {
            name: branch.name,
            commit: {
                sha: branch.commit.sha
            },
            protected: branch.protected
        };
    }
  • RepositoryAPI method that performs the actual GitHub API call to list branches.
    async listBranches(owner, repo, protected_only = false, page = 1, perPage = 30) {
        return this.client.get(`repos/${owner}/${repo}/branches`, {
            params: {
                protected: protected_only,
                page,
                per_page: perPage
            }
        });
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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?

Tool has no description.

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?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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

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