Skip to main content
Glama

jira_search_users

Search Jira users by name, username, or email to find usernames for assigning issues or filtering by assignee. Returns display names and usernames.

Instructions

Search for Jira users by name, username, or email. Use this to find usernames for assigning issues or filtering by assignee. Returns matching users with their display names and usernames.

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": {
      "query": "<query>"
    },
    "name": "jira_search_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch text - matches against username, display name, and email
startAtNoStarting index for pagination
maxResultsNoMaximum number of results

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose the shape of the result (matching users with display names and usernames), which is valuable given there is no output schema, but it says nothing about permissions needed to search users, result ordering, or whether the search is exact vs fuzzy.

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?

Three short sentences, front-loaded with the action and immediately followed by the use case and the return shape. Every sentence carries information; there is no filler.

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 simple three-parameter read tool with no output schema and no annotations, the description covers purpose, intended use, and return contents adequately. It falls short only on permission/auth expectations and the fact that paging is available, which the schema handles.

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 coverage is 100%, so query, startAt, and maxResults are all documented in the schema itself. The description's mention of matching against name, username, and email restates the query parameter description rather than adding new meaning, so baseline 3 applies.

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?

States a specific verb and resource ('Search for Jira users') plus the matching fields (name, username, email), which is clearer than a bare name restatement. It does not distinguish itself from the sibling jira_get_assignable_users, whose name implies overlapping intent, so an agent must still infer which one to pick.

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

Usage Guidelines4/5

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

Provides a concrete use case: finding usernames for assigning issues or filtering by assignee. That is clear positive guidance, but there are no exclusions or stated alternatives, so the boundary against jira_get_assignable_users is left implicit.

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