Skip to main content
Glama

push_files

Push multiple files to a GitHub repository in a single commit, specifying the owner, repo, branch, and commit message using the input schema.

Instructions

Push multiple files to a GitHub repository in a single commit

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
branchYesBranch to push to (e.g., 'main' or 'master')
filesYesArray of files to push
messageYesCommit message
ownerYesRepository owner (username or organization)
repoYesRepository name

Implementation Reference

  • Core handler function implementing the push_files tool logic: fetches current branch ref, creates a new git tree with the files, creates a commit, and updates the branch reference.
    export async function pushFiles(
      owner: string,
      repo: string,
      branch: string,
      files: FileOperation[],
      message: string
    ) {
      const refResponse = await githubRequest(
        `https://api.github.com/repos/${owner}/${repo}/git/refs/heads/${branch}`
      );
    
      const ref = GitHubReferenceSchema.parse(refResponse);
      const commitSha = ref.object.sha;
    
      const tree = await createTree(owner, repo, files, commitSha);
      const commit = await createCommit(owner, repo, message, tree.sha, [commitSha]);
      return await updateReference(owner, repo, `heads/${branch}`, commit.sha);
    }
  • Zod schema defining the input parameters for the push_files tool, including repo details, branch, files array, and commit message.
    export const PushFilesSchema = z.object({
      owner: z.string().describe("Repository owner (username or organization)"),
      repo: z.string().describe("Repository name"),
      branch: z.string().describe("Branch to push to (e.g., 'main' or 'master')"),
      files: z.array(FileOperationSchema).describe("Array of files to push"),
      message: z.string().describe("Commit message"),
    });
  • index.ts:90-94 (registration)
    Registers the push_files tool in the MCP server's listTools response, providing name, description, and JSON schema derived from PushFilesSchema.
    {
      name: "push_files",
      description: "Push multiple files to a GitHub repository in a single commit",
      inputSchema: zodToJsonSchema(files.PushFilesSchema),
    },
  • MCP server request handler for callTool requests to push_files: parses arguments with schema and delegates to files.pushFiles function.
    case "push_files": {
      const args = files.PushFilesSchema.parse(request.params.arguments);
      const result = await files.pushFiles(
        args.owner,
        args.repo,
        args.branch,
        args.files,
        args.message
      );
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
  • Supporting schema for individual file operations (path and content) used within PushFilesSchema's files array.
    export const FileOperationSchema = z.object({
      path: z.string(),
      content: z.string(),
    });
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic operation. It doesn't disclose critical behavioral traits like authentication requirements, rate limits, error handling, whether it overwrites existing files, or what happens on failure. The description is insufficient for a mutation tool with zero annotation coverage.

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?

The description is a single, efficient sentence that clearly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded with the core functionality.

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 mutation tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It lacks information about return values, error conditions, authentication requirements, and behavioral constraints that would help an agent use it correctly.

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 description coverage is 100%, so the schema already documents all 5 parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema, maintaining the baseline score of 3 for adequate but not enhanced parameter documentation.

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 specific action ('push multiple files'), resource ('to a GitHub repository'), and scope ('in a single commit'). It distinguishes from sibling tools like 'create_or_update_file' (which handles single files) by emphasizing batch operations.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'create_or_update_file' for single files or 'create_commit' for different commit structures. It lacks context about prerequisites, limitations, or typical use cases.

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

Related 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/tuanle96/mcp-github'

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