Skip to main content
Glama
KS-GEN-AI

Jira MCP Server

by KS-GEN-AI

assign_ticket

Assign Jira tickets to specific team members using account IDs to manage workload distribution and ticket ownership.

Instructions

Assign a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}/assignee. Do not use markdown in your query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdYesThe account id of the assignee
issueIdOrKeyYesThe issue id or key

Implementation Reference

  • The core handler function that executes the tool logic by sending a PUT request to the Jira API to assign the ticket (issue) to the specified accountId.
    async function assignTicket(
      accountId: string,
      issueIdOrKey: string,
    ): Promise<any> {
      try {
        const response = await axios.put(
          `${JIRA_URL}/rest/api/3/issue/${issueIdOrKey}/assignee`,
          {
            accountId,
          },
          {
            headers: getAuthHeaders().headers,
          },
        );
    
        return response.data;
      } catch (error: any) {
        return {
          error: error.response.data,
        };
      }
    }
  • Input schema definition for the assign_ticket tool, specifying required string parameters accountId and issueIdOrKey.
    inputSchema: {
      type: 'object',
      properties: {
        accountId: {
          type: 'string',
          description: 'The account id of the assignee',
        },
        issueIdOrKey: {
          type: 'string',
          description: 'The issue id or key',
        },
      },
      required: ['accountId', 'issueIdOrKey'],
  • src/index.ts:208-226 (registration)
    Tool registration in the MCP tools array, defining the name, description, and input schema.
    {
      name: 'assign_ticket',
      description:
        'Assign a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}/assignee. Do not use markdown in your query.',
      inputSchema: {
        type: 'object',
        properties: {
          accountId: {
            type: 'string',
            description: 'The account id of the assignee',
          },
          issueIdOrKey: {
            type: 'string',
            description: 'The issue id or key',
          },
        },
        required: ['accountId', 'issueIdOrKey'],
      },
    },
  • MCP request handler case that dispatches the assign_ticket tool call, validates inputs, invokes the assignTicket function, and formats the response.
    case 'assign_ticket': {
      const accountId: any = request.params.arguments?.accountId;
      const issueIdOrKey: any = request.params.arguments?.issueIdOrKey;
    
      if (!accountId || !issueIdOrKey) {
        throw new Error('Account id and issue id or key are required');
      }
    
      const response = await assignTicket(accountId, issueIdOrKey);
    
      return {
        content: [
          {
            type: 'text',
            text: 'Ticket assigned : ' + JSON.stringify(response, 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 mentions the API endpoint but doesn't disclose behavioral traits like whether this is a mutation (implied by 'assign'), authentication requirements, error handling, or what happens on success/failure. The note about markdown is irrelevant to behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It's concise but poorly structured. The first sentence states the purpose, but the second sentence about markdown is irrelevant and distracting. Front-loading is adequate, but the extra sentence doesn't earn its place, reducing effectiveness.

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 no annotations and no output schema, the description is incomplete for a mutation tool. It lacks context on permissions, side effects, response format, or error cases. Sibling tools suggest a Jira context, but this isn't leveraged to explain integration points.

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%, so parameters are fully documented in the schema. The description adds no meaning beyond what the schema provides (e.g., no context on how to obtain accountId or issueIdOrKey). Baseline 3 is appropriate as the schema does the heavy lifting.

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 ('Assign a ticket') and the target system ('on Jira'), with a specific API endpoint mentioned. It distinguishes from siblings like 'create_ticket' or 'edit_ticket' by focusing on assignment, but doesn't explicitly differentiate from 'query_assignable' which is related to assignee lookup.

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 a valid ticket and assignee), exclusions, or how it relates to siblings like 'query_assignable' (which might help find assignable users). The API endpoint detail is technical but not usage guidance.

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/KS-GEN-AI/jira-mcp-server'

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