Skip to main content
Glama
multiinstance-jira-mcp

multiinstance-jira-mcp

by jmeronon-dev

Search users

jira_search_users
Read-only

Search Jira users by name or email, and filter results to only those assignable to a specific project when a project key is supplied.

Instructions

Find users by name/email. With projectKey, only users assignable in that project are returned.

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": "jira_search_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
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.
maxResultsNo
projectKeyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description does add one genuinely non-obvious behavior: results are constrained to project-assignable users when projectKey is set. It says nothing about result caps, empty-query behavior, or how instance routing affects scope.

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 short sentences with zero filler; the core lookup behavior is front-loaded and the conditional filtering rule follows. Nothing could be removed without losing information.

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 4-parameter tool with no output schema and sparse schema descriptions, the definition covers lookup and filtering but omits what a caller gets back (e.g., accountId vs. display name), which matters for chaining into assignment tools. It is workable but leaves a meaningful gap.

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 only 25% (only 'instance' is documented), so the description carries real weight here: it explains that 'query' matches name/email and that 'projectKey' filters to assignable users. maxResults is left entirely to the schema, which does bound it 1-100.

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?

"Find users by name/email" gives a specific verb (find) and resource (users) with the lookup key, which separates it from jira_search (issues) and jira_whoami. It stops short of naming a sibling or stating the alternative, but the resource 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?

The projectKey sentence implies the main use case (resolving who is assignable before jira_assign_issue), but the description never states when to prefer this over other lookups or what happens when no query is supplied. Usage is implied rather than prescribed.

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