Skip to main content
Glama
kunwarVivek

mcp-github-project-manager

add_issues_to_sprint

Add GitHub issues to an existing sprint for organized project management and workflow tracking.

Instructions

Add issues to an existing sprint

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sprintIdYes
issueIdsYes

Implementation Reference

  • Main handler method in ProjectManagementService that loops through issueIds and calls sprintRepo.addIssue for each, returning success count and message.
    async addIssuesToSprint(data: {
      sprintId: string;
      issueIds: string[];
    }): Promise<{ success: boolean; addedIssues: number; message: string }> {
      try {
        let addedCount = 0;
        const issues = [];
    
        // Add each issue to the sprint
        for (const issueId of data.issueIds) {
          try {
            await this.sprintRepo.addIssue(data.sprintId, issueId);
            addedCount++;
            issues.push(issueId);
          } catch (error) {
            process.stderr.write(`Failed to add issue ${issueId} to sprint: ${error}`);
          }
        }
    
        return {
          success: addedCount > 0,
          addedIssues: addedCount,
          message: `Added ${addedCount} issue(s) to sprint ${data.sprintId}`
        };
      } catch (error) {
        throw this.mapErrorToMCPError(error);
      }
    }
  • ToolDefinition including name, description, input schema (addIssuesToSprintSchema), and examples for the add_issues_to_sprint tool.
    export const addIssuesToSprintTool: ToolDefinition<AddIssuesToSprintArgs> = {
      name: "add_issues_to_sprint",
      description: "Add issues to an existing sprint",
      schema: addIssuesToSprintSchema as unknown as ToolSchema<AddIssuesToSprintArgs>,
      examples: [
        {
          name: "Add issues to sprint",
          description: "Add multiple issues to an existing sprint",
          args: {
            sprintId: "sprint_1",
            issueIds: ["123", "124", "125"]
          }
        }
      ]
    };
  • Registration of sprint-related tools in ToolRegistry's registerBuiltInTools method, including addIssuesToSprintTool.
    this.registerTool(createSprintTool);
    this.registerTool(listSprintsTool);
    this.registerTool(getCurrentSprintTool);
    this.registerTool(updateSprintTool);
    this.registerTool(addIssuesToSprintTool);
    this.registerTool(removeIssuesFromSprintTool);
  • Private helper in GitHubSprintRepository that performs the actual GraphQL mutation to update project item field values, assigning issues to sprint (iteration).
    private async addIssuesToSprint(sprintId: string, issueIds: IssueId[]): Promise<void> {
      const addItemQuery = `
        mutation($input: UpdateProjectV2ItemFieldValueInput!) {
          updateProjectV2ItemFieldValue(input: $input) {
            projectV2Item {
              id
            }
          }
        }
      `;
    
      for (const issueId of issueIds) {
        await this.graphql(addItemQuery, {
          input: {
            projectId: this.config.projectId,
            itemId: `Issue_${issueId}`,
            fieldId: sprintId,
            value: "ITERATION",
          },
        });
      }
    }
  • Tool dispatching handler in main server index.ts that routes the tool call to ProjectManagementService.addIssuesToSprint.
    case "add_issues_to_sprint":
      return await this.service.addIssuesToSprint(args);
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 an 'add' operation (implying mutation), but doesn't disclose any behavioral traits: it doesn't mention permissions required, whether this is idempotent, what happens if issues are already in the sprint, error conditions, or what the response looks like. For a mutation tool 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 purpose without any wasted words. It's appropriately sized for a simple tool and gets straight to the point. Every word earns its place in conveying the essential action.

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?

Given this is a mutation tool with no annotations, 0% schema description coverage, and no output schema, the description is incomplete. It doesn't explain what happens after adding issues, error conditions, permissions needed, or relationship to sibling tools. For a tool that modifies data, more contextual information is needed for safe and effective use.

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 doesn't mention any parameters at all - it doesn't explain what 'sprintId' and 'issueIds' represent, their format, or constraints. While the parameter names are self-explanatory to some extent, the description adds zero semantic value beyond what's already inferable from the schema property names.

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 ('add') and target resource ('issues to an existing sprint'), making the purpose immediately understandable. It distinguishes this from sibling tools like 'create_sprint' (which creates new sprints) and 'remove_issues_from_sprint' (which does the opposite operation). However, it doesn't specify what type of 'issues' are being added (e.g., Jira issues, GitHub issues), which prevents 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. It doesn't mention prerequisites (e.g., that the sprint must already exist), nor does it differentiate from similar tools like 'assign_items_to_iteration' or explain when to use 'add_issues_to_sprint' versus 'create_issue' followed by this tool. The agent must infer usage from the tool 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

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/kunwarVivek/mcp-github-project-manager'

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