Skip to main content
Glama

Git Manage Tool

git_manage
Destructive

Manage external git repositories with atomic file, branch, commit, and pull request operations. Supports GitHub, GitLab, Bitbucket, and generic SSH.

Instructions

Connect, browse, and modify external git repositories (GitHub, GitLab, Bitbucket, generic SSH). Repo connections store encrypted credentials and use phpseclib for SSH. File and commit ops happen through the platform's AtomicCommittingGitClient so concurrent agent edits don't corrupt working trees.

Repo actions:

  • repo_list / repo_get (read).

  • repo_create (write) — name, url, credentials (object).

  • repo_update (write) — repo_id + any creatable field.

  • repo_delete (DESTRUCTIVE) — repo_id. Drops connection; does not delete the remote repo.

  • repo_test (read) — repo_id. Verifies connectivity + auth.

File / branch / commit actions:

  • file_read (read) — repo_id, path, optional branch.

  • file_write (write — pushes to remote) — repo_id, path, content, branch, message.

  • file_list (read) — repo_id, optional path, branch.

  • branch_create (write) — repo_id, name, source branch.

  • commit (write — pushes to remote) — repo_id, message, files[].

  • pr_create (write) — repo_id, title, body, source branch, target branch. Returns PR URL.

  • pr_list (read) — repo_id; optional state filter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: repo_list, repo_get, repo_create, repo_update, repo_delete, repo_test, file_read, file_write, file_list, branch_create, commit, pr_create, pr_list
deadline_msNoOptional: max wall-clock time (ms) the tool may spend. If exceeded during the call, returns a DEADLINE_EXCEEDED error. Minimum 100 ms. Leave unset for no deadline.
providerNoFilter by provider: github, gitlab, bitbucket, gitea, generic
modeNoFilter by mode: api_only, sandbox, bridge
statusNoFilter by status: active, disabled, error
limitNoMax results (default 15, max 100)
idYesRepository UUID
nameYesFriendly name for the repository
urlYesRepository URL (HTTPS or SSH)
default_branchNoDefault branch name (default: main)main
credential_idNoUUID of a Credential containing the PAT/SSH key for authentication
configNoMode-specific config. sandbox: {provider, instance_type, run_tests, test_command}. bridge: {repo_name, working_directory}. pr: {require_approval}
repository_idYesRepository UUID
pathYesFile path relative to repo root (e.g. "src/app.php")
refNoGit ref: branch name, tag, or commit SHA (default: HEAD)HEAD
contentYesFull file content to write
messageYesCommit message
branchNoBranch to commit to (defaults to repository default_branch)
fromNoSource branch or commit SHA to branch from (defaults to repository default_branch)
changesYesArray of file changes: [{path, content}] or [{path, deleted: true}]
titleYesPull request title
bodyNoPull request description/body
headYesSource branch (the branch with changes)
baseNoTarget branch (defaults to repository default_branch)
stateNoPR state filter: open, closed, all (default: open)open
Behavior5/5

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

Beyond the destructiveHint annotation, the description explicitly marks repo_delete as DESTRUCTIVE, notes that file_write and commit push to remote, details concurrency safety via AtomicCommittingGitClient, and explains encrypted credential storage. This adds rich behavioral context.

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?

The description is well-organized with bullet points grouping repo actions and file/branch/commit actions, and front-loads the main purpose. However, it is slightly verbose and could be more concise without losing clarity.

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

Completeness3/5

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

Given the complexity (25 parameters, many actions), the description covers main categories and behaviors (destructiveness, concurrency, push). However, it lacks return value information (no output schema), error handling notes, and does not clarify conditional parameter requirements (e.g., required fields depend on action). The required array in the schema is misleading without further explanation.

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%, with each parameter having a description in the schema. The tool description adds some context (e.g., repo_create uses credentials object, file_write pushes) but does not significantly elaborate on individual parameters beyond what the schema already provides. Baseline score of 3 is appropriate.

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 connects, browses, and modifies external git repositories, listing specific actions (e.g., repo_list, file_read, commit) and supported providers (GitHub, GitLab, etc.). This specificity distinguishes it from sibling tools like integration_execute or workflow_manage.

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 description enumerates all possible actions but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it. Usage is implied through action descriptions, but no comparative or contextual advice is given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/escapeboy/agent-fleet-o'

If you have feedback or need assistance with the MCP directory API, please join our Discord server