Jira Cloud MCP Server

get_issue_property

Retrieve a specific property value from a Jira issue by providing the issue key or ID and the property key. Get the data needed to inspect custom fields or metadata.

Instructions

Get issue property

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>",
      "propertyKey": "<propertyKey>"
    },
    "name": "get_issue_property"
  }
}

Input Schema

Name	Required	Description	Default
`propertyKey`	Yes	The key of the property.
`issueIdOrKey`	Yes	The key or ID of the issue.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 30, 2026

TDQS

C2.2/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. 'Get' implies a read operation, but the description does not disclose response format, permissions, error behavior, or side effects. It is accurate but minimally informative.

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

Conciseness2/5

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

The description is short and free of filler, but it is under-specified rather than appropriately concise. Three words do not provide enough context to justify the description's existence beyond the tool name. This is under-specification, not effective conciseness.

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?

The tool has no output schema, no annotations, and a description that only restates the name. While parameter semantics are covered by the schema, the description does not explain what an issue property is, what the caller receives, or how this differs from related issue endpoints. The context is insufficient for confident tool selection and expectation setting.

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%, and both parameters have clear descriptions in the input schema. The tool description itself adds no parameter-level detail, but the schema already provides sufficient meaning, so the baseline of 3 applies.

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

Purpose2/5

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

The description 'Get issue property' is essentially a rewording of the tool name and adds no detail about what an issue property is or what the operation entails. It fails to distinguish the tool from related property operations like set_issue_property or delete_issue_property. This is closer to a tautology than a functional explanation.

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 such as get_issue, set_issue_property, or delete_issue_property. There are no exclusions, prerequisites, or context hints. The agent is left to infer usage entirely from the tool name and sibling list.

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

Deploy Server