Skip to main content
Glama
multiinstance-jira-mcp

multiinstance-jira-mcp

by jmeronon-dev

List projects

jira_list_projects
Read-only

List Jira projects visible to your account, filter by key or name, and query multiple instances at once to merge results.

Instructions

List projects visible to the account. Supports several instances at once (instances / allInstances).

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_list_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoFilter by key or name.
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.
maxResultsNo
allInstancesNoRun against every configured instance and merge the results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 the safety profile is covered. The description adds the visibility scope ('visible to the account') and multi-instance merging, but omits pagination behavior, the maxResults cap of 100, and how merged results from several instances are combined or ordered.

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?

Two short sentences with the scope front-loaded and no filler. The second sentence largely restates what the schema already says about instances/allInstances, which is mild redundancy but not bloat.

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?

With no output schema and five optional parameters, the description never explains the return shape, whether results are paginated or truncated, or how keys/names in the response look. Adequate for selection but leaves real gaps for correct invocation and result interpretation.

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 coverage is 80%, so the schema already documents query, instance, instances, maxResults, and allInstances in detail. The description only echoes the instances/allInstances parameters and adds no format, syntax, or precedence guidance beyond them; 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?

States a specific verb and resource ('List projects') plus a scope qualifier ('visible to the account'), which an agent can act on directly. It doesn't distinguish itself explicitly from siblings, but the sibling set is mostly different resources (boards, sprints, statuses), so differentiation is less critical.

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?

Usage is only implied: the description notes multi-instance support but never says when to use 'instance' versus 'instances' versus 'allInstances', or when this tool is preferred over jira_search. An agent must infer the routing rules from the schema text.

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