ARCLinearGitHub-MCP

Overview Schema Source Related Servers Discussions Admin

github_list_branches

List branches in a GitHub repository, with optional parameters for repository name and maximum number of branches returned.

Instructions

List branches in a GitHub repository.

Args: repo: Repository name (defaults to configured default repo) limit: Maximum number of branches to return

Returns: Dictionary with list of branches

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description	Default
`repo`	No
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 13, 2026

TDQS

A3.6/5.0

Behavior2/5

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

With no annotations, the description carries full burden but only states it returns a dictionary. It does not disclose that it is read-only, any required authentication, rate limits, or constraints like pagination or error handling.

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 extremely concise with one sentence for purpose, two lines for parameters, and one line for returns. No redundant information; every sentence is valuable.

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

Completeness4/5

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

For a simple list tool with two optional parameters and no output schema, the description covers purpose, parameters, and return type. It lacks details on the return structure's fields or potential pagination, but it is adequate.

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

Parameters4/5

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

The description adds meaningful context to the parameters: it clarifies that repo defaults to a configured default repository (not just null) and that limit is the maximum number of branches. This goes beyond the schema's titles and defaults.

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 tool lists branches in a GitHub repository, using a specific verb 'list' and resource 'branches'. It distinguishes from sibling tools like github_create_branch and github_get_default_branch by explicitly indicating the action is listing.

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 github_get_default_branch or github_create_branch. It lacks any usage context or exclusions.

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