Jira Cloud MCP Server

set_issue_property

Set a custom property on a Jira issue by specifying the issue ID or key, the property key, and a JSON value. Use this to store additional metadata associated with the issue.

Instructions

Set 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>",
      "body": "<body>"
    },
    "name": "set_issue_property"
  }
}

Input Schema

Name	Required	Description
`body`	Yes	The value of the property. The value has to be a valid, non-empty [JSON](https://tools.ietf.org/html/rfc4627) value. The maximum length of the property value is 32768 bytes.
`propertyKey`	Yes	The key of the issue property. The maximum length is 255 characters.
`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.0

Behavior1/5

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It merely says 'Set issue property' and does not state whether the property is created or overwritten, whether permissions are required, whether the operation is idempotent, or what side effects occur. This is effectively no behavioral information.

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 only three words and entirely restates the tool name. This is under-specification rather than genuine concciseness; every word is wasted because it adds no information beyond the name.

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?

For a mutation tool with no annotations and no output schema, the description is far too minimal. While the schema fully documents parameters, the agent is left without any understanding of when this tool is appropriate or what behavior to expect, making the definition incomplete for safe 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 100%, and the schema documents all three parameters including constraints such as the property value being valid JSON up to 32768 bytes and the key max length of 255 characters. The description adds nothing beyond the schema, 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 'Set issue property' is a direct restatement of the tool name with no additional detail. It identifies the verb and resource but fails to distinguish this tool from siblings like get_issue_property, delete_issue_property, or edit_issue.

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?

There is no guidance about when to use this tool versus the many related sibling tools. Siblings like get_issue_property, delete_issue_property, and edit_issue are present but the description gives no context for choosing among them.

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

Deploy Server