Skip to main content
Glama
CzSadykov

jira-service-desk-mcp

by CzSadykov

create_customer_request

Create a support ticket in Jira Service Management by specifying the service desk, request type, and field values. Optionally raise on behalf of another user or add participants.

Instructions

Create a new customer request (ticket) in a service desk.

Tip: call get_request_type_fields first to discover required field IDs and valid values for the chosen request type.

Args: service_desk_id: The numeric ID of the service desk (e.g. "1"). request_type_id: The numeric ID of the request type (e.g. "10"). values_json: JSON object with field values. Example: {"summary": "VPN not working", "description": "Cannot connect since morning"} raise_on_behalf_of: (Optional) Account ID (Cloud) or username (Server/DC) to raise the request on behalf of another user. request_participants: (Optional) Comma-separated account IDs or usernames to add as request participants.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
service_desk_idYes
request_type_idYes
values_jsonYes
raise_on_behalf_ofNo
request_participantsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Describes the creation action and input parameters, but lacks details on permissions, idempotency, error handling, or side effects such as notifications. With no annotations, the description carries the full burden and could be more transparent.

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?

Well-structured with a front-loaded tip and clear parameter list. Compact but covers necessary details. Could be slightly more concise by removing redundancy with schema titles.

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?

Covers input and a prerequisite, but does not mention output format, error handling, or relationships with sibling tools like attach_file_to_request. An output schema exists, which alleviates some burden, but still missing context for full usage.

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?

Adds significant value beyond the input schema (0% coverage). Explains each parameter's purpose with examples for values_json and clarifies the format for raise_on_behalf_of and request_participants.

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?

Clearly states 'Create a new customer request (ticket) in a service desk' with a specific verb and resource. Distinguishes from siblings like get_request_type_fields via the tip.

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?

Provides a helpful tip to call get_request_type_fields first, guiding on prerequisite discovery. However, does not explicitly mention when not to use this tool or compare with alternatives like attach_file_to_request.

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/CzSadykov/jira-service-desk-mcp'

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