Skip to main content
Glama
raalarcon9705

raalarcon-jira-mcp-server

assign_issue

Assign a Jira issue to a specific user by providing the issue key and user account ID.

Instructions

Assign a Jira issue to a user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueKeyYesThe issue key to assign
assigneeYesThe account ID of the user to assign to

Implementation Reference

  • Handler function that executes the assign_issue tool logic: validates args using assignIssueSchema, calls jiraClient.assignIssue(), and returns success message.
    export async function handleAssignmentTool(
      name: string,
      args: Record<string, unknown>,
      jiraClient: JiraClient
    ) {
      switch (name) {
        case 'assign_issue': {
          const validatedArgs = await assignIssueSchema.validate(args);
          const _result = await jiraClient.assignIssue(validatedArgs);
          return {
            content: [
              {
                type: 'text',
                text: `Issue ${validatedArgs.issueKey} assigned successfully`,
              },
            ],
          };
  • Yup validation schema for assign_issue requiring issueKey (string) and assignee (string).
    // Schema for assigning issue
    export const assignIssueSchema = yup.object({
      issueKey: yup.string().required('Issue key is required'),
      assignee: yup.string().required('Assignee is required'),
    });
  • Tool registration object defining name 'assign_issue', description, and inputSchema with issueKey and assignee required properties.
    {
      name: 'assign_issue',
      description: 'Assign a Jira issue to a user',
      inputSchema: {
        type: 'object',
        properties: {
          issueKey: {
            type: 'string',
            description: 'The issue key to assign',
          },
          assignee: {
            type: 'string',
            description: 'The account ID of the user to assign to',
          },
        },
        required: ['issueKey', 'assignee'],
      },
  • JiraClient.assignIssue() helper method that calls the Jira API to edit an issue and set the assignee's accountId.
    // Assign issue
    async assignIssue(input: AssignIssueInput) {
      try {
        const response = await this.jira.issues.editIssue({
          issueIdOrKey: input.issueKey,
          fields: {
            assignee: { accountId: input.assignee },
          },
        });
        return response;
      } catch (error) {
        throw new Error(`Failed to assign issue: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
  • src/index.ts:90-95 (registration)
    Routing logic in the MCP server that dispatches assign_issue calls to handleAssignmentTool.
    } else if (
      name.startsWith('assign_issue') ||
      name.startsWith('get_users') ||
      name.startsWith('get_current_user')
    ) {
      return await handleAssignmentTool(name, args || {}, this.jiraClient);
Behavior2/5

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

No annotations are present, so the description should disclose behavioral traits. It only states the action without mentioning side effects (e.g., unassigning previous assignee), permissions, or response behavior, leaving the agent underinformed.

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 sentence without extraneous words. It is appropriately sized for a simple tool with two parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with two required parameters and no output schema. The description provides the essential action but lacks context about prerequisites, effects on other entities, or failure modes.

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%, so the description's addition is minimal. It does not add meaning beyond the parameter names and descriptions already present in the schema, yielding a baseline score.

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 'Assign' and the resource 'Jira issue', making the action unambiguous. It distinguishes from sibling tools like update_issue or transition_issue, but does not elaborate on the scope or effect of assignment.

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. Siblings include update_issue and transition_issue, which could overlap, but the description gives no conditions or exclusions.

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/raalarcon9705/jira-mcp'

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