Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

atlassian-mcp__jira_create_issue

Create a new Jira issue in the specified project. You can set arbitrary fields at creation via additional_fields (e.g. assignee, priority, labels, components) — required for projects that reject unassigned issues. Returns the created issue key and URL.

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": {
      "project_key": "<project_key>",
      "summary": "<summary>"
    },
    "name": "atlassian-mcp__jira_create_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
summaryYesIssue summary / title
issue_typeNoIssue type name (default 'Task'). Common values: Task, Bug, Story, Epic
descriptionNoIssue description (plain text, will be converted to ADF)
project_keyYesProject key (e.g. PROJ)
additional_fieldsNoAdditional fields to set at creation, as a JSON object of field ID to value (e.g. {"assignee": {"accountId": "abc123"}, "priority": {"name": "High"}, "labels": ["foo"]}). Caller is responsible for value shape — pass-through to the Jira API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare this is a non-read-only, non-destructive write. The description adds real value on top: it states what comes back ('the created issue key and URL') and warns that additional_fields is a raw pass-through where the caller owns value shape. It does not mention permission requirements or validation failures, so it is not a 5.

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?

Three tight sentences: what it does, how to set extra fields, what it returns. The purpose is front-loaded and no sentence is filler.

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 covers creation, the escape hatch for arbitrary fields, a known failure mode, and the return values, which compensates for the missing output schema. A note on required permissions or on discovering field IDs via jira_list_fields would make it complete.

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%, so every parameter is already documented in structured fields. The description's example fields (assignee, priority, labels, components) largely duplicate the JSON example already present in the additional_fields schema, adding little new meaning. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource+scope: 'Create a new Jira issue in the specified project.' That clearly separates it from jira_update_issue and jira_get_issue. It stops short of naming a sibling alternative explicitly, so it lands at 4 rather than 5.

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?

It gives one genuinely useful usage rule — additional_fields is 'required for projects that reject unassigned issues' — which tells the agent when to reach for that parameter. Beyond that there is no guidance on when to create vs. update, or what to do first (e.g. list_fields to discover custom field IDs).

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

All DataToRAG toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources