Skip to main content
Glama
multiinstance-jira-mcp

multiinstance-jira-mcp

by jmeronon-dev

Search issues with JQL

jira_search
Read-only

Search 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

NameRequiredDescriptionDefault
jqlYesJQL, e.g. 'assignee = currentUser() AND statusCategory != Done ORDER BY updated DESC'
fieldsNoAdditional fields to return (e.g. customfield_10016).
startAtNoData Center pagination offset.
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.
instancesNoRun against these instances and merge the results.
maxResultsNoPer instance (default 20).
allInstancesNoRun against every configured instance and merge the results.
nextPageTokenNoCloud pagination token from a previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/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 adds genuinely non-obvious behavior — results are grouped per instance and one instance's failure does not suppress the others. That partial-failure semantics is the kind of thing an agent cannot infer from structured fields. It does not mention pagination or result volume limits, which keeps it from a 5.

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 sentences, action first, then targeting and result semantics. Every clause carries information an agent needs; nothing is padding.

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 an 8-parameter, multi-instance query tool with no output schema, the description covers the two things an agent most needs to know: how to pick targets and how results/failures are aggregated. Remaining gaps (pagination strategy given both startAt and nextPageToken, response field layout) are minor and largely handled by the schema.

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 100%, so every parameter is already documented, including the routing rules for `instance` and the per-instance semantics of maxResults. The description only restates allInstances=true, which adds no meaning beyond the schema. Baseline 3 is appropriate.

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?

Opens with a specific verb and resource: "Run a JQL query." That is unambiguous and distinct from siblings like jira_get_issue or jira_list_projects. It stops short of stating what a query returns (issue list vs keys), so it is clear but not maximally specific.

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 description explains the targeting modes (single instance, list of instances, allInstances=true), which is real usage guidance for the multi-instance dimension. It gives no guidance on when to prefer jira_get_issue (known key) over a JQL search, nor any prerequisites, so usage is implied rather than bounded.

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