Skip to main content
Glama

remove_project_item

Remove items from GitHub projects by specifying project and item IDs to manage project boards and maintain organization.

Instructions

Remove an item from a GitHub project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYes
itemIdYes

Implementation Reference

  • Core handler function implementing the remove_project_item tool logic using GitHub GraphQL API mutation deleteProjectV2Item.
    async removeProjectItem(data: {
      projectId: string;
      itemId: string;
    }): Promise<{ success: boolean; message: string }> {
      try {
        const mutation = `
          mutation($input: DeleteProjectV2ItemInput!) {
            deleteProjectV2Item(input: $input) {
              deletedItemId
            }
          }
        `;
    
        interface DeleteProjectItemResponse {
          deleteProjectV2Item: {
            deletedItemId: string;
          };
        }
    
        await this.factory.graphql<DeleteProjectItemResponse>(mutation, {
          input: {
            projectId: data.projectId,
            itemId: data.itemId
          }
        });
    
        return {
          success: true,
          message: `Item ${data.itemId} has been removed from project ${data.projectId}`
        };
      } catch (error) {
        throw this.mapErrorToMCPError(error);
      }
    }
  • Zod schema defining input parameters for the remove_project_item tool: projectId and itemId.
    // Schema for remove_project_item tool
    export const removeProjectItemSchema = z.object({
      projectId: z.string().min(1, "Project ID is required"),
      itemId: z.string().min(1, "Item ID is required"),
    });
    
    export type RemoveProjectItemArgs = z.infer<typeof removeProjectItemSchema>;
  • Registration of the removeProjectItemTool in the central ToolRegistry during built-in tools initialization.
    this.registerTool(removeProjectItemTool);
  • Dispatch handler in main server that routes tool calls to the service implementation.
    case "remove_project_item":
      return await this.service.removeProjectItem(args);
  • Tool definition including name, description, schema reference, and usage examples.
    export const removeProjectItemTool: ToolDefinition<RemoveProjectItemArgs> = {
      name: "remove_project_item",
      description: "Remove an item from a GitHub project",
      schema: removeProjectItemSchema as unknown as ToolSchema<RemoveProjectItemArgs>,
      examples: [
        {
          name: "Remove item from project",
          description: "Remove an item from a project",
          args: {
            projectId: "PVT_kwDOLhQ7gc4AOEbH",
            itemId: "PVTI_lADOLhQ7gc4AOEbHzM4AOAJ7"
          }
        }
      ]
    };
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Remove' implies a destructive mutation, it doesn't specify whether this is reversible, what permissions are required, what happens to associated data, or what the response looks like. For a destructive operation with zero annotation coverage, this is a significant gap.

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 states the core action without unnecessary words. It's appropriately sized for a simple operation and front-loads the essential information.

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 2 parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain parameter semantics, behavioral implications, or usage context, leaving significant gaps for an agent to understand and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the schema provides no parameter documentation. The description mentions 'an item from a GitHub project' but doesn't explain what 'projectId' and 'itemId' represent, their expected formats, or where to obtain them. It adds minimal value beyond the parameter names themselves.

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 verb ('Remove') and resource ('an item from a GitHub project'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'remove_issues_from_sprint' or 'delete_project', which have similar destructive semantics but target different resources.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing project/item IDs from list operations), exclusions, or comparisons to similar tools like 'delete_project' or 'remove_issues_from_sprint'.

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/HarshKumarSharma/MCP'

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