Skip to main content
Glama
multiinstance-jira-mcp

multiinstance-jira-mcp

by jmeronon-dev

Assign issue

jira_assign_issue
Idempotent

Assigns a Jira issue to a specified user via 'me', email, display name, account ID, or username, or unassigns it with 'none'.

Instructions

Assign an issue. user accepts 'me', an email/display name, a Cloud accountId or a Data Center username. Use 'none' to unassign.

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": {
      "issue": "<issue>",
      "user": "<user>"
    },
    "name": "jira_assign_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYes
issueYesIssue key ('ABC-123'), instance-prefixed key ('work:ABC-123') or full browse URL ('https://acme.atlassian.net/browse/ABC-123').
instanceNoJira instance name (see jira_list_instances). Optional: calls are routed automatically by 'name:KEY' prefixes, issue URLs, project-key mapping, the default instance, or when only one instance exists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive, open-world mutation. The description adds the non-obvious behavior that passing 'none' unassigns rather than errors, which is real value beyond the annotations, but it says nothing about the Jira permission needed to assign or what happens when a name matches multiple users.

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?

Two sentences, zero filler, and both the action and the user-format rules are front-loaded. Nothing needs to be re-read or inferred to act.

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

Completeness4/5

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

For a three-parameter mutation with no output schema, the description covers the action, the sentinel value, and the identity formats the schema omits. Only the failure modes (insufficient permission, ambiguous user names) are unaddressed, a modest gap for this complexity level.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema documents 'issue' and 'instance' thoroughly but leaves 'user' with no description at 67% coverage. The description compensates by enumerating the accepted identities ('me', email/display name, Cloud accountId, Data Center username) and the 'none' sentinel, directly closing the one real gap.

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 names a specific verb and resource ('Assign an issue') and immediately qualifies the assignee formats, so it is distinguishable from siblings like jira_update_issue or jira_create_issue. It does not explicitly contrast itself with those siblings, but the action is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It supplies the key operational idiom ('none' to unassign) and the accepted forms of the user argument, which is genuine usage guidance. It stops short of telling the agent when to prefer this over jira_update_issue or when to first resolve a user via jira_search_users.

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