Jira Cloud MCP Server

get_change_logs_by_ids

Retrieve specific changelog entries for a Jira issue by passing its ID/key and a list of changelog IDs. Get precise change history details without fetching all logs.

Instructions

Get changelogs by IDs

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": {
      "issueIdOrKey": "<issueIdOrKey>",
      "body": "<body>"
    },
    "name": "get_change_logs_by_ids"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes	Request body (JSON object)
`issueIdOrKey`	Yes	The ID or key of the issue.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 30, 2026

TDQS

C2.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says 'Get', implying a read-only operation, but reveals nothing about required permissions, behavior with invalid changelog IDs, ordering of results, or error handling. The description is too minimal to give an agent confidence in side effects or limitations.

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

Conciseness3/5

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

The description is extremely terse and front-loaded with the verb, containing no filler words. However, it is a grammatical fragment rather than a clear sentence, and the brevity comes at the cost of important context. It is concise, but not ideally structured for comprehension.

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?

Given no annotations, no output schema, and a nested parameter object, the description is under-specified. It does not mention that the tool requires an issue identifier plus a list of changelog IDs, nor does it describe what is returned or how invalid IDs are handled. An agent would need to inspect the schema and infer behavior from the sibling tool names, which is insufficient for a reliable 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?

Schema description coverage is marked as 100%, so the schema already explains issueIdOrKey and the body structure. The description's 'by IDs' roughly maps to the changelogIds array but adds little beyond what the parameter names and schema already convey. It does not clarify that the IDs are changelog IDs or how they relate to the issueIdOrKey.

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

Purpose3/5

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

The description states a verb and resource ('Get changelogs') but the modifier 'by IDs' is ambiguous — it does not specify that these are changelog IDs for a specific issue. It does not clearly distinguish this tool from the sibling 'get_change_logs' (which likely returns all changelogs for an issue). The tool name hints at the meaning, but the description itself lacks precision.

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?

The description provides no guidance on when to use this tool versus alternatives. The sibling tool list includes 'get_change_logs', which probably returns all changelogs for an issue, but no distinction or selection criteria is given. An agent would have to infer usage from the schema and tool name.

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

Deploy Server