Skip to main content
Glama

GitHub list repositories

github_list_repositories
Read-only

List GitHub repositories you have access to via your connected GitHub account. Returns repository names, owners, default branches, and visibility. Use this first to discover owner and repo names before using other GitHub tools. Use the search filter when looking for a specific repository.

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_repositories"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of repositories to return.
searchNoOptional search filter to match against repository names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds what the caller gets back (names, owners, default branches, visibility), which matters since there is no output schema. It does not mention pagination behavior despite a default limit of 50, nor anything about credential/scope requirements.

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?

Three short sentences, front-loaded with what it lists, then return contents, then usage ordering. No filler and no repetition of the title.

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 two-parameter read tool with full schema coverage and no output schema, the description covers purpose, returns, and sequencing well. The only gap is what happens when more repositories exist than the limit returns.

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?

Schema coverage is 100%, so both parameters are already documented; the description only reinforces that the search filter is for targeting a specific repository and says nothing about the limit parameter's effect. Baseline 3 applies where the schema carries the load.

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?

States a specific verb and resource ('List GitHub repositories') plus the access scope ('you have access to via your connected GitHub account'), which distinguishes it from the other github_* siblings that operate on files, PRs, or workflow runs.

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

Usage Guidelines4/5

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

Explicitly says to call this first to discover owner/repo names before other GitHub tools and to use the search filter for a specific repository. It gives no exclusions against similar listing tools (e.g. list_gitops_repositories, list_related_repositories), but the sequencing guidance is strong.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.