Search issues with JQL
jira_searchSearch Jira issues with JQL across one or multiple configured instances; results are grouped per instance, and a failure on one instance does not hide the other results.
Instructions
Run a JQL query. Target one instance, a list of instances or all of them at once (allInstances=true) — results are grouped per instance and a failure on one instance does not hide the others.
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": {
"jql": "<jql>"
},
"name": "jira_search"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| jql | Yes | JQL, e.g. 'assignee = currentUser() AND statusCategory != Done ORDER BY updated DESC' | |
| fields | No | Additional fields to return (e.g. customfield_10016). | |
| startAt | No | Data Center pagination offset. | |
| instance | No | Jira 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. | |
| instances | No | Run against these instances and merge the results. | |
| maxResults | No | Per instance (default 20). | |
| allInstances | No | Run against every configured instance and merge the results. | |
| nextPageToken | No | Cloud pagination token from a previous page. |