Skip to main content
Glama
Sign In
@cloud9-labs/mcp-github

@cloud9-labs/mcp-github

by cloud9-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

github_list_branches

List branches from a GitHub repository by specifying owner and repo names. Use page and per_page for pagination when handling many branches.

Instructions

List branches in a repository

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "owner": "<owner>",
      "repo": "<repo>"
    },
    "name": "github_list_branches"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number
repoYesRepository name
ownerYesRepository owner username
per_pageNoResults per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It says only 'List branches' and does not mention pagination, return format, permissions, or whether this is a read-only operation. This is a significant gap for a tool with pagination parameters.

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 concise sentence with no unnecessary words. It is front-loaded and 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?

The tool has no output schema and no annotations, and the description is minimal. It does not explain what is returned (list of branch names? metadata?), pagination behavior, or any edge cases. This is insufficient for a tool with 4 parameters.

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?

All parameters (owner, repo, page, per_page) have descriptions in the schema, so schema coverage is 100%. The description adds no additional parameter semantics beyond what the schema already provides, warranting the baseline score of 3.

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 'List branches in a repository' clearly identifies the action (list) and resource (branches), making it distinct from sibling tools like list_commits or list_issues. It is unambiguous and specific.

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

Usage Guidelines3/5

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

The description gives no explicit guidance on when to use this tool versus alternatives. However, the name and description make the use case obvious (listing branches), so usage is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools