Skip to main content
Glama

jira_get_edit_meta

Retrieve editable fields and allowed values for a Jira issue before updating custom fields, so you can confirm field availability, schema type, and correct REST value shape.

Instructions

Get which fields can be edited on a specific issue, including schema type, operations, and allowedValues. This is GET /rest/api/2/issue/{key}/editmeta. Call this before writing custom fields so you know the REST value shape (string, number, {value}, {name} for Server users, arrays) and whether the field is on the edit screen. A field listed by jira_get_fields but missing here cannot be updated on that 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": {
      "issueKey": "<issueKey>"
    },
    "name": "jira_get_edit_meta"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueKeyYesIssue key to get edit metadata for (e.g., KP-123)
customOnlyNoSet to true to only return fields whose id is customfield_<digits>

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden and does well: it names the underlying endpoint, implies a read-only GET, and explains the semantic consequence of a field's absence. What it omits are operational specifics such as whether the response is large, whether it is cached, or permission requirements for reading edit metadata.

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?

Four tight sentences, front-loaded with purpose and followed by the pre-write guidance and the sibling contrast. The endpoint string 'GET /rest/api/2/issue/{key}/editmeta' is mildly redundant with the name but serves as useful anchoring for REST-oriented agents.

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

Completeness4/5

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

For a two-parameter read with no output schema, the description supplies enough: what comes back (types, operations, allowedValues), why it matters, and how to interpret gaps. It could be marginally stronger by noting that results are issue-scoped and vary per issue, but nothing needed to call it correctly is absent.

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 100% with both parameters documented in the schema, including the issueKey format example and the customfield_<digits> semantics of customOnly. The description adds no parameter-level detail beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource ('Get which fields can be edited on a specific issue') and enumerates the payload contents (schema type, operations, allowedValues). It actively distinguishes itself from the sibling jira_get_fields by explaining that a field present there but absent here is not editable.

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

Usage Guidelines5/5

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

Gives an explicit call-before rule ('Call this before writing custom fields') tied to a concrete goal (learning the REST value shape) and a concrete exclusion (fields missing here cannot be updated). The agent knows both when to invoke it and how to interpret a negative result.

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