Skip to main content
Glama

delete_project_column

Remove a project column in GitHub by specifying its unique column ID using the GitHub MCP Server. Streamline project management and maintain organized workflows.

Instructions

Delete a project column

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
column_idYesThe unique identifier of the column

Implementation Reference

  • The core handler function that executes the tool logic by sending a DELETE request to the GitHub API to delete the specified project column.
    export async function deleteProjectColumn(columnId: number) {
        try {
            const url = `https://api.github.com/projects/columns/${columnId}`;
    
            await githubRequest(url, {
                method: 'DELETE',
                headers: {
                    'Accept': 'application/vnd.github.inertia-preview+json'
                }
            });
    
            return { success: true };
        } catch (error) {
            if (error instanceof GitHubError) {
                throw error;
            }
    
            throw new GitHubError(`Failed to delete project column: ${(error as Error).message}`, 500, { error: (error as Error).message });
        }
    }
  • Zod schema for input validation of the delete_project_column tool, requiring the column_id.
    export const DeleteProjectColumnSchema = z.object({
        column_id: z.number().describe("The unique identifier of the column"),
    });
  • index.ts:240-244 (registration)
    Tool registration in the MCP server's listTools response, defining name, description, and input schema.
    {
      name: "delete_project_column",
      description: "Delete a project column",
      inputSchema: zodToJsonSchema(projects.DeleteProjectColumnSchema),
    },
  • Server-side handler in the CallToolRequest that parses input, invokes the deleteProjectColumn function, and returns the formatted response.
    case "delete_project_column": {
      const args = projects.DeleteProjectColumnSchema.parse(request.params.arguments);
      const result = await projects.deleteProjectColumn(args.column_id);
      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?

No annotations are provided, so the description carries full burden. It states 'Delete' which implies a destructive mutation, but doesn't disclose critical behaviors: whether deletion is permanent or reversible, what happens to associated cards (e.g., moved or deleted), required permissions, or error conditions (e.g., invalid column_id). This leaves significant gaps for a destructive operation.

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, direct sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient. No structural issues or redundancy are present.

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 destructive mutation tool with no annotations and no output schema, the description is insufficient. It lacks details on behavior (e.g., side effects, permissions), output (e.g., success confirmation or error messages), and context relative to siblings (e.g., how it differs from 'delete_card'). Given the complexity and risk of deletion, more completeness is needed.

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%, with the parameter 'column_id' documented as 'The unique identifier of the column'. The description doesn't add any meaning beyond this, such as where to obtain the ID or format examples. Baseline 3 is appropriate since the schema adequately defines the parameter.

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 ('Delete') and resource ('a project column'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'delete_card' or 'delete_issue' beyond the resource name, nor does it specify what type of project (e.g., GitHub Project v1 vs v2) it refers to, which is relevant given siblings like 'list_project_columns' and 'update_project_column'.

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 is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing column_id from 'list_project_columns'), exclusions (e.g., cannot delete columns with cards), or related tools like 'update_project_column' for modifications instead of deletion. The agent must infer usage from the name alone.

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