jc-mcp

Get Jira Issues (batch)

jcm_getIssues

Read-onlyIdempotent

Batch-read up to 50 Jira issues in one call, returning summaries, descriptions, and recent comments in request order so you can review many issues without individual requests.

Instructions

Batch-read up to 50 Jira issues in one call (one JQL search, plus one GET per key the search omits). Returns an array in request order, one entry per unique key: {key, summary, type, status, parent ({key, summary, type} or null), description (markdown or null), comments: [{author, body, created}], commentsTotal?}. fields selects description and/or comments (default both). Descriptions are capped at maxDescriptionChars (default 600), comment bodies at maxCommentChars (default 300); cut text ends with "… [truncated, N chars total]". Only the 3 most recent comments are returned (oldest first); commentsTotal appears when more exist. A key that is missing or not visible to you returns {key, error} instead of being dropped. A moved/renamed key returns the issue under the requested key plus movedTo (current key). Use jcm_getIssue for full detail on one issue.

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": {
      "issueKeys": "<issueKeys>"
    },
    "name": "jcm_getIssues"
  }
}

Input Schema

Name	Required	Description
`fields`	No	Which content to include (default both). key, summary, type, status, parent are always returned
`issueKeys`	Yes	Jira issue keys, e.g. ["PROJ-1", "PROJ-2"] (max 50; duplicates collapsed)
`maxCommentChars`	No	Per-comment body cap in chars (default 300)
`maxDescriptionChars`	No	Description cap in chars (default 600)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.12.0Nov 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses the return array shape, per-field truncation caps with defaults and the exact truncation marker, that only the 3 most recent comments are returned oldest-first with commentsTotal, that invisible/missing keys return {key, error} rather than being dropped, and that moved keys add movedTo. These are the failure-mode and data-fidelity details an agent cannot infer from structured fields.

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?

Front-loaded with the core action and result shape, then layered with the operational caveats; every sentence carries information. It is dense and quite long for a paragraph, but no sentence is filler.

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

Completeness5/5

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

There is no output schema and no annotations covering data-shape, so the description carries that burden fully—return shape, truncation, ordering, comment limit, error entries, and moved-key handling are all covered. Nothing an agent needs to invoke or interpret this tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning: fields selects description/comments with key/summary/type/status/parent always returned, and both caps default to specific values with the resulting truncation format. It reinforces rather than merely repeats the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Batch-read up to 50 Jira issues in one call') and explains the mechanics (one JQL search plus one GET per omitted key). It is clearly distinguished from the sibling jcm_getIssue, which is named as the single-issue alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly points to jcm_getIssue for full detail on one issue, giving an agent a clear routing rule for the batch-vs-single decision. It does not spell out a when-not-to-use case beyond that (e.g., very large result sets or searching by criteria, which jcm_searchIssues covers), so it stops just short of a 5.

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