Skip to main content
Glama

create_repository

Create a new GitHub repository in your account by specifying its name, description, privacy, and optional README initialization.

Instructions

Create a new GitHub repository in your account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesRepository name
descriptionNoRepository description
privateNoWhether repo should be private
autoInitNoInitialize with README

Implementation Reference

  • Comment header indicating the start of the 'Create Repository' tool registration.
    )
    
    // Tool: Create Repository
  • The 'server.tool("create_repository", ...)' call that registers the tool with its name, description, and input schema.
    server.tool(
    	"create_repository",
    	"Create a new GitHub repository in your account",
    	{
    		name: z.string().describe("Repository name"),
    		description: z.string().optional().describe("Repository description"),
    		private: z
    			.boolean()
    			.optional()
    			.describe("Whether repo should be private"),
    		autoInit: z.boolean().optional().describe("Initialize with README"),
    	},
    	async ({ name, description, private: isPrivate, autoInit }) => {
    		try {
    			const response = await octokit.rest.repos.createForAuthenticatedUser({
    				name,
    				description,
    				private: isPrivate,
    				auto_init: autoInit,
    			})
    			const r = response.data
    			return {
    				content: [{ type: "text", text: `Repository created: **${r.full_name}**\nURL: ${r.html_url}\nVisibility: ${r.private ? "private" : "public"}\nDefault branch: ${r.default_branch}` }],
    			}
    		} catch (e: any) {
    			return {
    				content: [{ type: "text", text: `Error: ${e.message}` }],
    			}
    		}
    	},
    )
  • Zod schema defining the input parameters: name (required string), description (optional string), private (optional boolean), autoInit (optional boolean).
    {
    	name: z.string().describe("Repository name"),
    	description: z.string().optional().describe("Repository description"),
    	private: z
    		.boolean()
    		.optional()
    		.describe("Whether repo should be private"),
    	autoInit: z.boolean().optional().describe("Initialize with README"),
    },
  • Async handler function that calls octokit.rest.repos.createForAuthenticatedUser() with the input params and returns a formatted success/error response.
    async ({ name, description, private: isPrivate, autoInit }) => {
    	try {
    		const response = await octokit.rest.repos.createForAuthenticatedUser({
    			name,
    			description,
    			private: isPrivate,
    			auto_init: autoInit,
    		})
    		const r = response.data
    		return {
    			content: [{ type: "text", text: `Repository created: **${r.full_name}**\nURL: ${r.html_url}\nVisibility: ${r.private ? "private" : "public"}\nDefault branch: ${r.default_branch}` }],
    		}
    	} catch (e: any) {
    		return {
    			content: [{ type: "text", text: `Error: ${e.message}` }],
    		}
    	}
    },
Behavior2/5

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

With no annotations, the description fails to disclose behavioral traits such as authentication requirements, error handling (e.g., if repo exists), or whether the operation is idempotent. Only the basic creation action is stated.

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?

Single sentence, efficient, and front-loaded with the core action. No unnecessary words.

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 creation tool with 4 parameters and no output schema, the description lacks context on default behaviors (e.g., public vs private default), naming constraints, or success/failure indications. Incomplete for an agent.

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% and each parameter has a description in the schema. The description adds no additional semantics beyond the schema, so 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 verb (create), resource (GitHub repository), and scope (in your account), making it distinct from sibling tools like fork_repository or get_repository.

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?

No guidance on when to use this tool versus alternatives (e.g., create_issue, create_branch). No prerequisites or exclusions mentioned.

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

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