Skip to main content
Glama

jira_assign_issue

Assign or unassign Jira issues to specific users by providing the issue key and assignee username. Use this tool to manage issue ownership in your Jira workflow.

Instructions

Assign or unassign a Jira issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueKeyYesThe Jira issue key
assigneeYesUsername to assign (null to unassign)

Implementation Reference

  • Core implementation of the jira_assign_issue tool: calls Jira REST API to assign or unassign an issue by PUT to /issue/{issueKey}/assignee with {name: username} (null to unassign).
    async assignIssue(issueKey: string, username: string | null): Promise<void> {
      await this.request<void>(`/issue/${issueKey}/assignee`, {
        method: "PUT",
        body: JSON.stringify({ name: username }),
      });
    }
  • MCP CallToolRequestHandler switch case for 'jira_assign_issue': validates arguments with AssignIssueSchema and delegates to jiraClient.assignIssue, returns success message.
    case "jira_assign_issue": {
      const { issueKey, assignee } = AssignIssueSchema.parse(args);
      await jiraClient.assignIssue(issueKey, assignee);
      return {
        content: [
          {
            type: "text",
            text: assignee
              ? `Issue ${issueKey} assigned to ${assignee}`
              : `Issue ${issueKey} unassigned`,
          },
        ],
      };
    }
  • Zod input schema definition for the jira_assign_issue tool used for validation in the handler.
    const AssignIssueSchema = z.object({
      issueKey: z.string().describe("The Jira issue key"),
      assignee: z
        .string()
        .nullable()
        .describe("Username to assign (null to unassign)"),
    });
  • src/index.ts:309-323 (registration)
    Tool registration entry returned by ListToolsRequestHandler, including name, description, and JSON input schema.
    {
      name: "jira_assign_issue",
      description: "Assign or unassign a Jira issue",
      inputSchema: {
        type: "object",
        properties: {
          issueKey: { type: "string", description: "The Jira issue key" },
          assignee: {
            type: ["string", "null"],
            description: "Username to assign (null to unassign)",
          },
        },
        required: ["issueKey", "assignee"],
      },
    },
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 mentions the tool can 'assign or unassign', implying mutation, but doesn't disclose behavioral traits like required permissions, whether changes are reversible, rate limits, or what happens on success/failure. 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 extremely concise and front-loaded in a single sentence, with zero wasted words. It efficiently communicates the core functionality without unnecessary elaboration, earning the highest score for brevity and clarity.

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 the tool's complexity as a mutation operation with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects, error handling, and return values, making it inadequate for safe and effective use by an AI agent.

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 adds minimal value beyond the input schema, which has 100% coverage. It implies 'assignee' can be null for unassignment, but the schema already states this. With high schema coverage, the baseline is 3, and the description doesn't provide additional syntax or format details.

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 tool's purpose with specific verbs ('assign' and 'unassign') and resource ('a Jira issue'), making it immediately understandable. However, it doesn't differentiate from sibling tools like 'jira_update_issue' or 'jira_transition_issue' which might also affect issue assignment, so it doesn't reach the highest 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. With siblings like 'jira_update_issue' that might handle assignment as part of broader updates, there's no explicit when/when-not context or mention of prerequisites, leaving usage ambiguous.

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/yogeshhrathod/JiraMCP'

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