Skip to main content
Glama

List GitOps repositories

list_gitops_repositories
Read-only

List the repositories a GitHub or Bitbucket Cloud credential can reach for GitOps. Use after list_gitops_credentials to let the user pick a repository for GitOps setup at cluster creation. Returns the provider and each repository's full name and default branch; a Bitbucket Cloud repository also carries workspace and repo_slug, which a create takes as gitops_workspace and gitops_repo_slug.

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": {
      "credential_id": "<credential_id>"
    },
    "name": "list_gitops_repositories"
  }
}

Input Schema

NameRequiredDescriptionDefault
credential_idYesUUID of the GitHub or Bitbucket Cloud credential to list repositories for. Get this from list_gitops_credentials.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

readOnlyHint=true already tells the agent this is a safe read. The description goes beyond that by disclosing the returned shape (provider, full name, default branch) and the provider-specific variation for Bitbucket Cloud (workspace and repo_slug), which is genuine behavioral context the annotations cannot carry.

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 sentences, front-loaded with the purpose, then the sequencing, then the return contract. Nothing is repeated from the title or wasted, and the downstream field mapping is packed into the final clause.

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

Completeness5/5

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

With no output schema, the description fully compensates by naming the return fields and the Bitbucket-specific extras, and it ties those to the create-side gitops_workspace/gitops_repo_slug inputs. Nothing an agent needs to call this correctly or hand off to a create is missing.

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?

There is a single required parameter and schema coverage is 100%, with the schema already explaining that credential_id comes from list_gitops_credentials. The description adds no new format or constraint detail for credential_id itself, so the schema is doing the work here.

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 opens with a specific verb and resource ('List the repositories') and immediately scopes it to what a GitHub or Bitbucket Cloud credential can reach for GitOps. That scope alone separates it from generic siblings such as github_list_repositories or list_related_repositories.

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?

It states an explicit prerequisite and sequence ('Use after list_gitops_credentials') plus the downstream intent ('let the user pick a repository for GitOps setup at cluster creation'). It stops short of naming when NOT to use it or pointing at the sibling that lists non-GitOps repos, so it is clear context without full exclusions.

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.