Skip to main content
Glama

list_repositories

Read-only

Lists the authenticated user's GitHub repositories with name, language, stars, visibility and last push, plus matching totals. Use to find, count, or filter repos by visibility, topic or language.

Instructions

List the authenticated user's own GitHub repositories (name, description, language, stars, visibility, last push), plus the total number that match. Use for questions about WHICH repos exist, counting repos, or finding a repo by topic or language. Do NOT use for details of one named repo (use get_repository) or for issues, pull requests or commits.

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": "list_repositories"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoOrder repos by 'updated' (most recently changed first), 'pushed', 'created' or 'full_name'.updated
limitNoMaximum number of items to return (1-50). Totals are reported separately, so a small limit is fine when only a count is needed.
visibilityNoWhich repos to include: 'all', 'public' or 'private'.all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds meaningful scope that annotations cannot convey — the results are limited to the authenticated user's own repos, not org or third-party repos. It also discloses a non-obvious return trait: a separate total-matching count accompanies the capped list. It does not mention pagination or rate-limit behavior, which keeps it below a 5.

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?

Two tight sentences: the first front-loads what is returned, the second routes usage and exclusions. No filler, repetition or hedging, and the enumeration of returned fields is compact rather than verbose.

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?

There is no output schema, so the description usefully enumerates the shape of each result plus the accompanying total, which is exactly the missing information. The one incomplete spot is the suggestion that repos can be located by topic or language when the parameter set supports neither, which could mislead an agent into expecting a filter it doesn't have.

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 sort, limit and visibility are already fully documented, making 3 the baseline. The description adds no parameter-specific syntax or defaults, and it slightly overpromises by implying the agent can "find a repo by topic or language" even though no topic or language filter parameter exists.

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 the authenticated user's own GitHub repositories") and enumerates the returned fields (name, description, language, stars, visibility, last push) plus the match total. It is clearly distinguishable from get_repository and from issue/PR tools, which are named explicitly.

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

Usage Guidelines5/5

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

Gives positive selection criteria ("questions about WHICH repos exist, counting repos, or finding a repo by topic or language") and explicit exclusions with the correct redirect ("Do NOT use for details of one named repo (use get_repository)"). Both when-to-use and when-not-to-use are covered with the alternative named.

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