Jira Cloud MCP Server

find_bulk_assignable_users

Find users assignable to one or more Jira projects by filtering on name, email, or account ID, enabling bulk assignment tasks.

Instructions

Find users assignable to projects

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": {
      "projectKeys": "<projectKeys>"
    },
    "name": "find_bulk_assignable_users"
  }
}

Input Schema

Name	Required	Description
`query`	No	A query string that is matched against user attributes, such as `displayName` and `emailAddress`, to find relevant users
`startAt`	No	The index of the first item to return in a page of results (page offset).
`username`	No	This parameter is no longer available. See the [deprecation notice](https://developer.atlassian.com/cloud/jira/platform/
`accountId`	No	A query string that is matched exactly against user `accountId`. Required, unless `query` is specified.
`maxResults`	No	The maximum number of items to return per page.
`projectKeys`	Yes	A list of project keys (case sensitive). This parameter accepts a comma-separated list.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 30, 2026

TDQS

C2.9/5.0

Behavior2/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 explaining behavior. It only states the read-oriented purpose and does not disclose pagination, default result limits, the deprecated username parameter, or the query/accountId mutual-exclusivity. This is a minimal disclosure for a search/list tool with no explicit behavior beyond 'find'.

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

Conciseness4/5

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

The description is six words and front-loads the core action and resource, with no filler. It earns its place as a title-like summary. However, the extreme brevity leaves useful usage and behavioral context for other dimensions rather than this one.

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?

This is a 6-parameter tool with one required key, no annotations, no output schema, and a close sibling find_users; the single-sentence description is not enough to select or invoke it confidently. Important operational details such as query/accountId exclusivity, pagination defaults, and distinction from find_users are absent. The description covers purpose only, so the overall definition is incomplete for correct invocation.

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 already documents all six parameters with 100% coverage, so the baseline is 3. The description adds no parameter-specific meaning beyond framing projectKeys in the context of assignability. It does not clarify the relationship between query and accountId or the paging parameters.

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 uses a specific verb ('Find'), names the resource ('users'), and qualifies the scope ('assignable to projects'), which distinguishes it from generic siblings like find_users. It is concise and leaves little ambiguity about the action. It does not explicitly mention 'bulk' or contrast with sibling search tools, so it falls just short of top marks.

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?

No guidance is provided for when to use this tool rather than find_users or other user-related tools. There are no stated exclusions, prerequisites, or alternative conditions. The only implied usage is from the purpose phrase itself, so an agent must infer when this variant applies.

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

Deploy Server