Skip to main content
Glama

Gitea: List repositories

gitea_list_repositories
Read-only

List Gitea repositories for a user, organization, or the authenticated account and return repository metadata.

Instructions

[UNIFIED] List Gitea repositories for a user/organization or current user. Returns repository list with metadata.

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": {
      "site": "<site>"
    },
    "name": "gitea_list_repositories"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
siteYes
typeNoall
limitNo
ownerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

B3.1/5.0
Behavior3/5

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

readOnlyHint=true already declares this is a safe read, so the description only needs to add context. It adds that results are repositories 'with metadata' and that scoping is by owner or current user, but says nothing about pagination behavior despite page/limit parameters, sorting, or whether non-existent owners error or return empty.

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

Conciseness4/5

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

Two tight sentences with the resource and scope front-loaded; nothing is wasted. The '[UNIFIED]' tag is unexplained jargon that occupies space without conveying actionable meaning.

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?

For a 5-parameter tool with zero schema coverage and no output schema, the description is too thin: the required 'site' parameter, the 'type' filter values, and pagination defaults are all undocumented anywhere. An agent can guess at owner behavior but not at the required argument.

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

Parameters2/5

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

Schema description coverage is 0% across 5 parameters, so the description must carry the burden. It only clarifies that 'owner' means user/organization and that omitting it means current user; it leaves the required 'site' parameter, the 'type' filter (default 'all', no enum given), and the page/limit semantics completely unexplained.

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

Purpose4/5

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

States a specific verb and resource (List Gitea repositories) plus the scope: a specific user/organization or the current user, and notes the return payload. The '[UNIFIED]' marker hints it subsumes the more specific gitea_list_org_repos and gitea_list_user_repos siblings, though it never names them, so differentiation from those siblings is only inferable.

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 phrase 'for a user/organization or current user' implies two usage modes but never says when to pick this over gitea_list_org_repos or gitea_list_user_repos, nor any prerequisite (auth, site selection). Usage is implied rather than prescribed.

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