Skip to main content
Glama
proprock
by proprock

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JIRA_EMAILYesEmail address associated with the API token
JIRA_BASE_URLYesJira Cloud site URL, such as https://example.atlassian.net
JIRA_API_TOKENYesJira Cloud API token

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_issuesA

Search Jira Cloud issues with JQL. Returns items and an opaque next_page_token (null on the last page); pass it back as page_token for the next page. limit is 1..100 (default 20); 0 is invalid. fields replaces the default fields entirely -- default: summary, status, issuetype, priority, assignee, updated, project. fields=[] returns only the issue key.

get_issueA

Fetch one issue by key. fields replaces the default fields entirely -- default: summary, description, issuetype, status, priority, assignee, reporter, labels, components, created, updated, resolutiondate, issuelinks, project, parent, subtasks. fields=[] returns the key with no fields. Requesting 'watches' or 'votes' resolves the real watcher/voter list (watch_count/is_watching/watchers, vote_count/has_voted/voters) via one extra request per field, instead of Jira's own link-only stub. When fields names any customfield_*, the result adds field_names mapping each returned customfield id to its display name. 'transitions' lists the moves available now (id, name, resulting status), the same names transition_issue accepts. Does not include comments, attachments, or changelog history; use the dedicated tools for those.

get_commentsA

List an issue's comments. order='desc' (default) returns newest first; 'asc' returns oldest first. start_at/limit paginate the logical, filtered, sorted collection (ties broken by comment id); limit=0 returns every remaining comment from start_at with no 100-comment cap. since (ISO-8601 with an explicit offset) keeps only comments created at or after that instant, and total reflects the filtered collection.

get_attachmentsA

List an issue's attachment metadata (id, filename, mime_type, size, author, created) without downloading content. Use download_attachment to fetch a file's bytes.

download_attachmentA

Download one attachment by id into a process-scoped temporary cache and return its local_path. The cache is removed when the server shuts down.

get_changelogA

List an issue's field-change history. order='desc' (default) returns newest first; 'asc' returns oldest first. start_at/limit paginate the logical, sorted collection (ties broken by entry id); limit=0 returns every remaining entry from start_at with no cap. Each entry lists human-readable field changes.

add_commentA

Add one comment to an issue. body is Markdown -- headings, lists, fenced code blocks, bold/italic, inline code, links -- converted to Jira's rich text; anything outside that set stays literal. Returns the created comment in the same shape get_comments returns. This server cannot edit or delete a comment afterwards.

transition_issueA

Move an issue through its workflow. to is a transition name or the name of the status to reach, matched ignoring case and surrounding space. A transition's name often differs from the status it leads to (a transition called 'In Progress' can produce status 'In Development'), and two transitions can reach one status, so prefer the transition name; if nothing matches, the error lists every available transition and its resulting status. comment is Markdown and is posted in the same call as the move. Changes issue state.

update_issueA

Set issue fields, taking the same values get_issue returns: summary as text, description as Markdown, assignee as an account id, an email, a display name, or the literal "me" (an ambiguous name is an error listing the candidates), labels as a list, components and priority by name, duedate as YYYY-MM-DD, parent as an issue key, and any customfield_* or unknown field as raw Jira JSON. null clears assignee, description, priority, parent, or duedate. labels and components REPLACE the whole list, so read the issue first if you mean to add one. Cannot change status (use transition_issue) or add a comment (use add_comment).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 9 tools

Disambiguation5/5

Each tool targets a distinct resource or action: search vs. fetch, comments, attachment metadata vs. download, changelog, add comment, transition, update. The get_issue description explicitly excludes comments, attachments, and changelog, and get_attachments vs. download_attachment are clearly separated by metadata vs. content.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with lowercase and underscores: search_issues, get_issue, get_comments, get_attachments, download_attachment, get_changelog, add_comment, transition_issue, update_issue. No mixing of conventions.

Tool Count5/5

9 tools is well within the ideal 3-15 range, and each tool covers a distinct aspect of Jira issue interaction without redundancy or bloat.

Completeness2/5

The set is missing create_issue and delete_issue, which are core lifecycle operations for an issue tracker. While it covers reading, updating, transitioning, and adding comments, the absence of create/delete is a significant gap that will cause agent failures when those actions are needed.

Maintenance

ActivityMaintained
ResponsivenessNo issues