Skip to main content
Glama

jira_bulk_create

Bulk-create JIRA issues and wire dependency links between them in a single call. Supports aliases for intra-batch linking and provides a per-item success report for easy retry of failures.

Instructions

Bulk-create JIRA issues and (optionally) wire dependency links between them in one call — built for epic decomposition. issues are created in order and each may carry a local alias. links are created afterward; each inward/outward is resolved alias-first (to the freshly-minted key) else treated as an existing issue key, so you can link issues this same call just created. Default is continue-on-error: every record is attempted and a YAML report lists per-issue {alias, ok, key, self_url | error}, per-link {ok | error}, and a summary. Set fail_fast to stop at the first failure. NOTE: JIRA has no transaction — nothing is rolled back; the report always shows exactly what succeeded so you can retry only the remainder. To link existing issues only, pass an empty issues array and reference real keys in links.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linksNoDependency links to create after the issues. Each endpoint is resolved alias-first (to the freshly-minted key), else treated as an existing issue key.
issuesYesIssues to create, in order. May be empty to only create `links` between existing issues.
fail_fastNoWhen true, stop at the first failed create or link instead of continuing. The partial report is still returned. Defaults to false (continue-on-error).
Behavior5/5

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

No annotations provided, but the description explicitly discloses critical behaviors: no transaction (nothing rolled back), alias resolution order, default continue-on-error, and the report format showing exactly what succeeded. This fully compensates for missing annotations.

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 a single well-structured paragraph with no wasted words. Every sentence adds critical context, covering purpose, behavior, parameters, and edge cases efficiently.

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

Completeness5/5

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

Despite no output schema, the description thoroughly explains the YAML report format and retry guidance. It covers edge cases (empty issues, existing keys) and provides complete context for an agent to use the tool effectively.

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

Parameters4/5

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

Schema coverage is 100% with detailed descriptions. The description adds value by explaining the alias resolution mechanism and how issues and links interact, going beyond the schema's per-parameter descriptions.

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 the tool's function: bulk-create JIRA issues and optionally wire dependency links in one call, specifically for epic decomposition. It distinguishes itself from single-create and link tools.

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

Usage Guidelines4/5

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

The description provides clear usage context (epic decomposition) and explains default behavior (continue-on-error) and fail_fast option. It also notes that passing an empty issues array allows linking existing issues. However, it could explicitly state when to prefer this over sequential jira_create + jira_link_create calls.

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