Skip to main content
Glama
Sign In
GitHub MCP Server — AutomateHub

GitHub MCP Server — AutomateHub

by gnvidia06-ux
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Crear commit (agregar o modificar archivo)

create_commit

Creates or replaces a file in a GitHub repository by committing the full content, with optional owner and branch; use it to add or update files such as READMEs or scripts.

Instructions

Hace un commit en un repositorio de GitHub creando un archivo nuevo o reemplazando el contenido de uno existente. Usala cuando el usuario pida agregar, escribir, actualizar o subir un archivo (por ejemplo un README o un script) a un repo. El contenido enviado reemplaza al archivo completo. Si no se indica branch, usa la principal.

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": {
      "repo": "<repo>",
      "path": "<path>",
      "content": "<content>",
      "message": "<message>"
    },
    "name": "create_commit"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesRuta del archivo dentro del repo. Ejemplo: 'README.md' o 'src/index.js'.
repoYesNombre del repositorio, sin el owner. Ejemplo: 'mi-proyecto'.
ownerNoUsuario u organización dueña del repositorio. Si se omite, se usa el usuario autenticado (dueño del token).
branchNoBranch donde hacer el commit. Si se omite, se usa la branch principal del repo.
contentYesContenido completo del archivo en texto plano. Si el archivo existe, se reemplaza.
messageYesMensaje del commit. Ejemplo: 'docs: agrega guía de instalación'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden and does useful work: it warns that the submitted content replaces the entire file and that the default branch is the main one. It says nothing about authentication, whether the commit lands directly on the branch without a PR, or how conflicts or errors are surfaced.

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?

Four short sentences, front-loaded with the action and followed by the trigger, the replacement semantics, and the branch default. The branch sentence partly repeats the schema, but nothing is padded.

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?

For a six-parameter mutation tool with no annotations and no output schema, the description covers purpose, trigger, replacement semantics, and the branch default. It leaves out what the call returns (e.g., commit SHA), permission requirements, and failure behavior, which an agent calling a write operation would want.

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 repo, path, owner, branch, content, and message are all already documented in the schema. The description's note about the default branch duplicates what the branch parameter already says and adds no syntax or format meaning beyond it.

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: makes a commit in a GitHub repo by creating a new file or replacing an existing one. That clearly separates it from create_repository and create_branch, though it never names a sibling explicitly to route the agent.

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?

Gives an explicit trigger: use it when the user asks to add, write, update, or upload a file (README, script) to a repo. It supplies no when-not conditions or alternatives, so the agent must infer that branch creation belongs to create_branch.

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