Skip to main content
Glama
Sign In
MCP Jira Server

MCP Jira Server

by vuphuongminh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

jira_assign_issue

Assign a Jira issue to a user by supplying the issue key and assignee username, enabling task ownership updates in self-hosted Jira.

Instructions

Assign a Jira issue to a user

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "issueKey": "<issueKey>",
      "assignee": "<assignee>"
    },
    "name": "jira_assign_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
assigneeYesUsername to assign the issue to
issueKeyYesThe Jira issue key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the core action but does not reveal whether the assignee is replaced, whether permissions are required, whether notifications fire, or whether the assignment is idempotent. For a mutating operation, this is minimal.

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, direct sentence with no filler. Every word contributes to identifying the operation, and it is immediately clear what the tool does.

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?

For a simple two-parameter assign operation, the description plus schema is arguably callable, but the lack of annotations, output schema, and usage or behavioral guidance leaves some practical uncertainty. It is minimally viable but not rich enough for an agent to fully anticipate side effects or result behavior.

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 the schema already documents both parameters. The description adds little beyond calling the assignee a 'user', which is a reasonable high-level gloss but does not enrich the schema's semantics meaningfully.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Assign'), names the exact resource ('a Jira issue'), and identifies the target ('a user'). This cleanly distinguishes it from sibling tools like jira_create_issue, jira_update_issue, or jira_add_comment, even without explicitly naming them.

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 gives no guidance on when to use this tool versus alternatives such as jira_update_issue, which could conceivably also handle assignment. There is no mention of prerequisites, when assignment is appropriate, or why this tool should be preferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools