Skip to main content
Glama

create_project

Automate the creation of a new project in a GitHub repository by specifying the owner, repository name, and project details. Simplify repository management with structured project setup.

Instructions

Create a new project in a GitHub repository

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoDescription of the project
nameYesName of the project
ownerYesRepository owner (username or organization)
repoYesRepository name

Implementation Reference

  • Core handler function that performs the POST request to GitHub API to create a new project in the specified repository.
    export async function createProject(owner: string, repo: string, name: string, body?: string) {
        try {
            const url = `https://api.github.com/repos/${owner}/${repo}/projects`;
    
            const response = await githubRequest(url, {
                method: 'POST',
                body: {
                    name,
                    body: body || '',
                }
            });
    
            return response;
        } catch (error) {
            if (error instanceof GitHubError) {
                throw error;
            }
    
            throw new GitHubError(`Failed to create project: ${(error as Error).message}`, 500, { error: (error as Error).message });
        }
    }
  • Zod schema defining the input parameters for the create_project tool: owner, repo, name, and optional body.
    export const CreateProjectSchema = z.object({
        owner: z.string().describe("Repository owner (username or organization)"),
        repo: z.string().describe("Repository name"),
        name: z.string().describe("Name of the project"),
        body: z.string().optional().describe("Description of the project"),
    });
  • index.ts:200-204 (registration)
    Tool registration in the ListTools response, defining name, description, and input schema.
    {
      name: "create_project",
      description: "Create a new project in a GitHub repository",
      inputSchema: zodToJsonSchema(projects.CreateProjectSchema),
    },
  • Dispatch handler in the CallToolRequest switch statement that parses arguments and calls the projects.createProject function.
    case "create_project": {
      const args = projects.CreateProjectSchema.parse(request.params.arguments);
      const result = await projects.createProject(
        args.owner,
        args.repo,
        args.name,
        args.body
      );
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a creation operation, implying mutation, but doesn't mention permissions required, rate limits, whether it's idempotent, or what happens on success/failure. For a mutation tool with zero annotation coverage, this leaves significant gaps.

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, clear sentence with zero wasted words. It's appropriately sized and front-loaded with the essential information about what the tool does.

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 no annotations and no output schema, the description is insufficient. It doesn't explain what happens after creation, error conditions, or behavioral aspects. The description should provide more context given the complexity of creating a project in GitHub.

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?

The description doesn't mention any parameters at all, but schema description coverage is 100% (all 4 parameters have descriptions in the schema). According to the rules, when schema coverage is high (>80%), the baseline is 3 even with no parameter information in the description.

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?

The description clearly states the action ('Create a new project') and the resource ('in a GitHub repository'), which is specific and unambiguous. However, it doesn't distinguish this from sibling tools like 'create_project_v2' or 'create_repository', which would require explicit differentiation for a perfect score.

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_project_v2' or 'create_repository', nor does it mention prerequisites or context for usage. It simply states what the tool does without any usage context.

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