Skip to main content
Glama
Sign In
Jira Cloud MCP Server

Jira Cloud MCP Server

by pascalhubacher
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_user

Fetch a Jira user's profile and attributes using their account ID, with expand options to include more details.

Instructions

Get user

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoThis parameter is no longer available. See the [deprecation notice](https://developer.atlassian.com/cloud/jira/platform/
expandNoUse [expand](#expansion) to include additional information about users in the response. This parameter accepts a comma-s
usernameNoThis parameter is no longer available. See the [deprecation notice](https://developer.atlassian.com/cloud/jira/platform/
accountIdNoThe account ID of the user, which uniquely identifies the user across all Atlassian products. For example, *5b10ac8d82e0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.9/5.0
Behavior1/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It provides none beyond the verb 'Get', which merely repeats the tool name; it does not mention outdated parameters, authentication needs, response shape, or side-effect safety.

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

Conciseness2/5

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

The description is technically short, but this is under-specification rather than efficient conciseness. The two words 'Get user' do not earn their place because they add no information beyond the tool name.

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

Completeness1/5

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

With four parameters, two of them deprecated, no required parameters, and no output schema, this description is far from complete. An agent cannot tell how to identify the user, what optional behaviors expand accepts, or what the response will look like.

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 all four parameters, including deprecation notes and the meaning of accountId. The description itself adds no parameter-level meaning, but the baseline of 3 applies because the structured schema is sufficient.

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

Purpose2/5

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

The description 'Get user' is a near-verbatim restatement of the tool name and provides no additional specificity. It does not indicate what kind of user data is returned, how the user is identified, or how this differs from sibling tools like find_users.

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?

There is no guidance on when to choose get_user over find_users, find_bulk_assignable_users, or get_issue_watchers. The description contains no context, prerequisites, or exclusions, so an agent receives no help in routing between alternatives.

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