Skip to main content
Glama
imrnbeg

Jira MCP Server

by imrnbeg

Get Jira Issue Comments

get_jira_issue_comments

Retrieve paginated comments for a Jira issue to track discussion history and collaboration details. Specify issue key and adjust pagination parameters to access relevant conversation data.

Instructions

Retrieve comments for a Jira issue with pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueIdOrKeyYesIssue key or ID (e.g., PROJ-123)
startAtNoPagination start index (default 0)
maxResultsNoPage size (1-100, default 50)

Implementation Reference

  • The handler function for the 'get_jira_issue_comments' tool. It constructs a URL for the Jira REST API endpoint to fetch comments for the specified issue, handles pagination parameters, fetches the data, processes the comments into a structured format (including id, author, dates, and body), and returns either structured content or an error response.
    async (args: { issueIdOrKey: string; startAt?: number; maxResults?: number }) => {
      try {
        const params = new URLSearchParams();
        if (typeof args.startAt === "number") params.set("startAt", String(args.startAt));
        if (typeof args.maxResults === "number") params.set("maxResults", String(args.maxResults));
        const url = `${JIRA_URL}/rest/api/3/issue/${encodeURIComponent(args.issueIdOrKey)}/comment${params.toString() ? `?${params.toString()}` : ""}`;
        const response = await fetch(url, { method: "GET", headers: getJiraHeaders() });
        if (!response.ok) {
          const errorText = await response.text();
          return { content: [{ type: "text", text: `Failed to get comments for ${args.issueIdOrKey}: ${response.status} ${response.statusText}\n${errorText}` }], isError: true };
        }
        const data = await response.json() as any;
        const comments = (data.comments || []).map((c: any) => ({ id: c.id, author: c.author?.displayName, created: c.created, updated: c.updated, body: typeof c.body === 'string' ? c.body : JSON.stringify(c.body) }));
        return { content: [{ type: "text", text: `Found ${data.total ?? comments.length} comments (showing ${comments.length}).` }], structuredContent: { issueIdOrKey: args.issueIdOrKey, total: data.total ?? comments.length, startAt: data.startAt ?? 0, maxResults: data.maxResults ?? comments.length, comments, raw: data } };
      } catch (error) {
        return { content: [{ type: "text", text: `Error getting comments for ${args.issueIdOrKey}: ${error instanceof Error ? error.message : String(error)}` }], isError: true };
      }
    }
  • Zod input schema defining the parameters for the tool: issueIdOrKey (required string), startAt (optional non-negative integer), maxResults (optional integer between 1-100). Includes descriptions for each.
    inputSchema: {
      issueIdOrKey: z.string().describe("Issue key or ID (e.g., PROJ-123)"),
      startAt: z.number().int().min(0).optional().describe("Pagination start index (default 0)"),
      maxResults: z.number().int().min(1).max(100).optional().describe("Page size (1-100, default 50)"),
    },
  • src/server.ts:309-338 (registration)
    The mcp.registerTool call that registers the 'get_jira_issue_comments' tool, providing the name, metadata (title, description), input schema, and the handler function.
    mcp.registerTool(
      "get_jira_issue_comments",
      {
        title: "Get Jira Issue Comments",
        description: "Retrieve comments for a Jira issue with pagination.",
        inputSchema: {
          issueIdOrKey: z.string().describe("Issue key or ID (e.g., PROJ-123)"),
          startAt: z.number().int().min(0).optional().describe("Pagination start index (default 0)"),
          maxResults: z.number().int().min(1).max(100).optional().describe("Page size (1-100, default 50)"),
        },
      },
      async (args: { issueIdOrKey: string; startAt?: number; maxResults?: number }) => {
        try {
          const params = new URLSearchParams();
          if (typeof args.startAt === "number") params.set("startAt", String(args.startAt));
          if (typeof args.maxResults === "number") params.set("maxResults", String(args.maxResults));
          const url = `${JIRA_URL}/rest/api/3/issue/${encodeURIComponent(args.issueIdOrKey)}/comment${params.toString() ? `?${params.toString()}` : ""}`;
          const response = await fetch(url, { method: "GET", headers: getJiraHeaders() });
          if (!response.ok) {
            const errorText = await response.text();
            return { content: [{ type: "text", text: `Failed to get comments for ${args.issueIdOrKey}: ${response.status} ${response.statusText}\n${errorText}` }], isError: true };
          }
          const data = await response.json() as any;
          const comments = (data.comments || []).map((c: any) => ({ id: c.id, author: c.author?.displayName, created: c.created, updated: c.updated, body: typeof c.body === 'string' ? c.body : JSON.stringify(c.body) }));
          return { content: [{ type: "text", text: `Found ${data.total ?? comments.length} comments (showing ${comments.length}).` }], structuredContent: { issueIdOrKey: args.issueIdOrKey, total: data.total ?? comments.length, startAt: data.startAt ?? 0, maxResults: data.maxResults ?? comments.length, comments, raw: data } };
        } catch (error) {
          return { content: [{ type: "text", text: `Error getting comments for ${args.issueIdOrKey}: ${error instanceof Error ? error.message : String(error)}` }], isError: true };
        }
      }
    );
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It mentions pagination, which is useful behavioral context, but doesn't cover other important aspects like authentication requirements, rate limits, error handling, or what the return format looks like. This is a minimal but not comprehensive disclosure.

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, efficient sentence that directly states the tool's function and key behavioral trait (pagination). It's front-loaded with no wasted words, making it highly concise and well-structured.

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?

Given the tool's moderate complexity (a read operation with pagination), no annotations, and no output schema, the description is minimally adequate. It covers the core purpose and pagination but lacks details on authentication, errors, or return values, leaving gaps for the agent to infer.

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 the schema already fully documents all three parameters. The description adds no additional meaning beyond what's in the schema (e.g., it doesn't explain comment structure or pagination details), meeting the baseline for high schema coverage.

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 clearly states the verb 'retrieve' and the resource 'comments for a Jira issue', making the purpose unambiguous. However, it doesn't explicitly distinguish this tool from sibling tools like 'get_jira_issue' which might also return comments, so it doesn't reach the highest score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'get_jira_issue' that might include comments, there's no indication of when this specific comment-focused tool is preferred, leaving usage unclear.

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

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