Skip to main content
Glama
freema

mcp-jira-stdio

by freema
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

jira_create_subtask

Creates a Jira subtask under a parent issue. Automatically selects the correct project and subtask type, and supports setting priority, assignee, labels, components, and description format.

Instructions

Creates a subtask under an existing parent issue. Automatically determines the correct project and subtask issue type. Supports setting priority, assignee, labels, and components. Description format is controlled by the "format" parameter (default: markdown).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoDescription format: "markdown" (converts Markdown to ADF), "adf" (use as-is ADF object), "plain" (converts plain text to ADF with basic formatting). Default: "markdown"markdown
labelsNoSubtask labels
summaryYesSubtask summary/title
assigneeNoAssignee account ID
priorityNoSubtask priority
componentsNoComponent names
descriptionNoSubtask description. Accepts plain text or ADF object.
parentIssueKeyYesParent issue key

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv1.11.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / description / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {}
+]
  2. Changed13 schema fields changedv1.10.2
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / assignee / description
      Previous value: -"Assignee account ID (optional)"New value: +"Assignee account ID"
    • removedInput schema / properties / components / default
      Removed value: -[]
    • changedInput schema / properties / components / description
      Previous value: -"Component names (optional)"New value: +"Component names"
    • addedInput schema / properties / description / anyOf
      Added value: +[
+  {
+    "type": "string"
+  }
+]
    • changedInput schema / properties / description / description
      Previous value: -"Detailed subtask description (optional)"New value: +"Subtask description. Accepts plain text or ADF object."
    • removedInput schema / properties / description / type
      Removed value: -"string"
    • addedInput schema / properties / format
      Added value: +{
+  "default": "markdown",
+  "description": "Description format: \"markdown\" (converts Markdown to ADF), \"adf\" (use as-is ADF object), \"plain\" (converts plain text to ADF with basic formatting). Default: \"markdown\"",
+  "enum": [
+    "markdown",
+    "adf",
+    "plain"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / labels / default
      Removed value: -[]
    • changedInput schema / properties / labels / description
      Previous value: -"Subtask labels (optional)"New value: +"Subtask labels"
    • changedInput schema / properties / parentIssueKey / description
      Previous value: -"Parent issue key (e.g., PROJECT-123)"New value: +"Parent issue key"
    • changedInput schema / properties / priority / description
      Previous value: -"Subtask priority name (e.g., High, Medium, Low) - optional"New value: +"Subtask priority"
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations are minimal (readOnlyHint=false). The description adds behavioral context (automatic project/type detection, format control) but lacks details on auth requirements, rate limits, or error conditions.

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?

Three sentences, front-loaded with action and key features. Efficient use of words, no redundancy.

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

Completeness3/5

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

No output schema; description doesn't mention return values or error handling. Covers main points but lacks completeness for a tool with 8 parameters.

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%, so descriptions already document parameters. The description adds value by highlighting the format parameter's role but does not significantly enhance parameter understanding.

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 creates a subtask under an existing parent issue, with automatic project and issue type detection. It distinguishes from siblings like jira_create_issue (top-level) and jira_update_issue.

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

Usage Guidelines3/5

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

The description implies use for subtasks but does not explicitly state when to use this tool vs alternatives (e.g., jira_create_issue). No when-not-to-use or prerequisites are mentioned.

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/freema/mcp-jira-stdio'

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