Skip to main content
Glama

jira_search_users

Find Jira users by username to assign tasks, mention in comments, or manage project teams. Enter a search query to locate specific users within your Jira instance.

Instructions

Search for Jira users

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesUsername search query

Implementation Reference

  • Core handler function that performs the actual Jira API call to search users by username query.
    async searchUsers(query: string): Promise<JiraUser[]> {
      return this.request<JiraUser[]>(
        `/user/search?username=${encodeURIComponent(query)}`
      );
    }
  • MCP server dispatch handler for the tool call, validates input and delegates to JiraClient.
    case "jira_search_users": {
      const { query } = SearchUsersSchema.parse(args);
      const users = await jiraClient.searchUsers(query);
      return {
        content: [{ type: "text", text: JSON.stringify(users, null, 2) }],
      };
    }
  • Input schema validation using Zod for the tool parameters.
    const SearchUsersSchema = z.object({
      query: z.string().describe("Username search query"),
    });
  • src/index.ts:390-400 (registration)
    Tool registration in the MCP listTools response, defining name, description, and input schema.
    {
      name: "jira_search_users",
      description: "Search for Jira users",
      inputSchema: {
        type: "object",
        properties: {
          query: { type: "string", description: "Username search query" },
        },
        required: ["query"],
      },
    },
  • TypeScript interface defining the structure of JiraUser objects returned by the tool.
    export interface JiraUser {
      self: string;
      key: string;
      name: string;
      emailAddress: string;
      displayName: string;
      active: boolean;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Search for Jira users' implies a read-only operation but doesn't specify authentication requirements, rate limits, pagination behavior, or what constitutes a valid search (e.g., partial matches, case sensitivity). This leaves significant gaps for an agent to understand how to use it effectively.

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, efficient sentence with zero wasted words. It's appropriately sized for a simple search tool and front-loads the essential information without unnecessary elaboration.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the search returns (e.g., user objects with fields like email, display name), potential limitations (e.g., only active users), or error conditions. For a tool with no structured behavioral data, this minimal description leaves too many unknowns.

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?

The input schema has 100% description coverage with the 'query' parameter documented as 'Username search query.' The description doesn't add any additional meaning beyond this, such as search syntax examples or result format hints. With high schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.

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 'Search for Jira users' clearly states the action (search) and resource (Jira users), making the purpose immediately understandable. However, it doesn't differentiate this from potential sibling tools like 'jira_get_current_user' or other user-related operations, which prevents a perfect score.

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 provides no guidance on when to use this tool versus alternatives. With multiple sibling tools available (like jira_get_current_user for a specific user or jira_search_issues for different resources), there's no indication of context, prerequisites, or exclusions for this search operation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yogeshhrathod/JiraMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server