Skip to main content
Glama
rust-works

omni-dev

by rust-works
OverviewSchemaRelated ServersScoreDiscussions
Rust
Local

jira_write

Update a JIRA issue's description, parent, assignee, reporter, or custom fields. Accepts markdown or ADF JSON for content.

Instructions

Update a JIRA issue. content updates the description (JFM markdown by default, or raw ADF JSON when format = "adf"); omit it to leave the description unchanged. JFM is GitHub-style markdown — see resource omni-dev://specs/jfm for syntax. parent sets the system parent field for hierarchy (Epic → Story, Story → Sub-task) — distinct from jira_link actions, which create relationship links (Blocks, Composition, etc.) rather than the parent field. assignee/reporter accept an accountId (use the empty string "" to clear, "-1" for JIRA automatic assignment); call jira_user_search first if you only have a name or email. fields is an escape hatch — a map of canonical JIRA field id to its API JSON value (e.g. {"priority": {"name": "High"}}) — for fields without a typed parameter. At least one of content, parent, assignee, reporter, or fields must be supplied.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assigneeNoAssignee `accountId`. The empty string `""` clears the assignee; `"-1"` triggers JIRA automatic assignment. Use `jira_user_search` to resolve a name or email to an `accountId`.
contentNoNew description body. Interpreted per `format`. Omit to leave the existing description unchanged (useful when only updating `parent`/`assignee`/`reporter`/`fields`). For `format = "jfm"` (the default), this is GitHub-style markdown, NOT JIRA wiki markup. Use `##` not `h2.`, triple-backtick fences not `{code}`, backtick inline code not `{{...}}`. Full reference: MCP resource `omni-dev://specs/jfm`.
fieldsNoAdditional `fields` keys merged into the issue update payload as-is. Keys must already be canonical JIRA field ids (e.g. `priority`, `labels`, `customfield_10010`). Values must already be in the API's JSON shape (e.g. `{"name": "High"}` for priority, `["a", "b"]` for labels). Setting `assignee` or `reporter` here collides with the typed parameters and is rejected — pass the typed parameter instead.
formatNoContent format — `jfm` (default) parses Markdown/JFM; `adf` accepts a raw ADF JSON document.
keyYesJIRA issue key (e.g., `PROJ-123`).
parentNoParent issue key (e.g., `PROJ-100`). When set, establishes a parent-child hierarchy on the issue (Epic → Story, Story → Sub-task, etc.). Distinct from `jira_link` actions, which create "Composition"-style links rather than the system parent field.
reporterNoReporter `accountId`. Same conventions as `assignee` (`""` clears, `"-1"` is JIRA automatic).

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavior: how content is interpreted per format, that omitting content leaves description unchanged, the special values for assignee/reporter, and the distinction between parent field and link relationships.

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

Conciseness5/5

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

The description is concise and well-structured, front-loading the main purpose. Every sentence adds value, with no redundant information. It efficiently packs detailed guidance into a single paragraph.

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?

The description thoroughly covers all parameters and their interactions, but it does not mention what the tool returns after a successful update (e.g., updated issue representation). Given the tool has no output schema, including return info would enhance completeness.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant meaning: explains the relationship between content and format, gives examples (e.g., empty string to clear assignee), clarifies that fields is an escape hatch, and distinguishes parent from jira_link actions.

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?

The description clearly states it updates a JIRA issue and lists the updatable fields (content, parent, assignee, reporter, fields). It distinguishes from sibling tools like jira_link and jira_create by noting that parent sets the system parent field unlike link actions.

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?

Provides explicit usage guidance: when to use jira_user_search, how to clear assignee/reporter, notes that parent is distinct from links, warns against setting assignee/reporter in fields, and specifies that at least one of content/parent/assignee/reporter/fields must be supplied.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rust-works/omni-dev'

If you have feedback or need assistance with the MCP directory API, please join our Discord server