Skip to main content
Glama

Get My Issues

get_my_issues

Retrieve all Jira issues currently assigned to you to track tasks and manage workload efficiently.

Instructions

Get all issues currently assigned to the configured CURRENT_USER

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
issuesNo

Implementation Reference

  • The async handler function that executes the get_my_issues tool logic: constructs JQL for current user's non-Done issues, calls searchIssues helper, formats output or error.
    async () => {
      try {
        const jql = `assignee = ${CURRENT_USER} AND status != Done ORDER BY updated DESC`;
        const issues = await searchIssues(jql);
        const output = { issues };
        return {
          content: [{ type: 'text', text: JSON.stringify(output, null, 2) }],
          structuredContent: output,
        };
      } catch (error) {
        const output = formatError(error);
        return {
          content: [{ type: 'text', text: JSON.stringify(output, null, 2) }],
          structuredContent: output,
          isError: true,
        };
      }
  • Input (empty) and output schema for get_my_issues tool using Zod validation.
      title: 'Get My Issues',
      description: 'Get all issues currently assigned to the configured CURRENT_USER',
      inputSchema: {},
      outputSchema: {
        issues: z.array(z.object({
          key: z.string(),
          summary: z.string(),
          status: z.string(),
          priority: z.string(),
          updated: z.string(),
        })).optional(),
        error: z.object({
          message: z.string(),
          statusCode: z.number().optional(),
          details: z.unknown().optional(),
        }).optional(),
      },
    },
  • src/index.ts:72-111 (registration)
    MCP server registration of the get_my_issues tool including schema and inline handler.
    server.registerTool(
      'get_my_issues',
      {
        title: 'Get My Issues',
        description: 'Get all issues currently assigned to the configured CURRENT_USER',
        inputSchema: {},
        outputSchema: {
          issues: z.array(z.object({
            key: z.string(),
            summary: z.string(),
            status: z.string(),
            priority: z.string(),
            updated: z.string(),
          })).optional(),
          error: z.object({
            message: z.string(),
            statusCode: z.number().optional(),
            details: z.unknown().optional(),
          }).optional(),
        },
      },
      async () => {
        try {
          const jql = `assignee = ${CURRENT_USER} AND status != Done ORDER BY updated DESC`;
          const issues = await searchIssues(jql);
          const output = { issues };
          return {
            content: [{ type: 'text', text: JSON.stringify(output, null, 2) }],
            structuredContent: output,
          };
        } catch (error) {
          const output = formatError(error);
          return {
            content: [{ type: 'text', text: JSON.stringify(output, null, 2) }],
            structuredContent: output,
            isError: true,
          };
        }
      }
    );
  • The searchIssues helper function called by the handler to perform JQL search on Jira API and map results to simplified issue objects.
    export async function searchIssues(jql: string, fields: string[] = ['summary', 'status', 'priority', 'updated']): Promise<JiraIssue[]> {
      const params = new URLSearchParams({
        jql,
        maxResults: '100',
      });
      // Add fields as separate params (the new API accepts array-style)
      fields.forEach(f => params.append('fields', f));
    
      const response = await jiraFetch<{
        issues: Array<{
          key: string;
          id: string;
          fields: {
            summary: string;
            status: { name: string };
            priority: { name: string };
            updated: string;
            description?: unknown;
            assignee?: { displayName: string; accountId: string };
            reporter?: { displayName: string; accountId: string };
            created?: string;
            comment?: { comments: Array<{ id: string; author: { displayName: string }; body: unknown; created: string; updated: string }> };
          };
        }>;
        isLast?: boolean;
        nextPageToken?: string;
      }>(`/search/jql?${params.toString()}`);
    
      return response.issues.map((issue) => ({
        key: issue.key,
        summary: issue.fields.summary,
        status: issue.fields.status.name,
        priority: issue.fields.priority?.name || 'None',
        updated: issue.fields.updated,
        assignee: issue.fields.assignee?.displayName,
      }));
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it 'gets all issues' but doesn't disclose behavioral traits like pagination, rate limits, authentication needs, or what 'all issues' entails (e.g., open/closed status). The description is minimal and lacks critical operational context.

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 front-loads the core functionality without any wasted words. It's appropriately sized for a simple tool with no parameters.

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 has no parameters and an output schema exists, the description is minimally complete. However, with no annotations and a read operation, it should ideally mention behavioral aspects like return format or scope, but the output schema mitigates some gaps. It's adequate but has clear room for improvement.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add parameter semantics, but this is appropriate given the empty schema, warranting a baseline score of 4.

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 ('Get') and resource ('issues currently assigned to the configured CURRENT_USER'), making the purpose specific and understandable. It distinguishes from siblings like 'search_issues' by focusing on user-assigned issues, though it doesn't explicitly name alternatives.

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 usage context (retrieving issues assigned to the current user), but doesn't provide explicit guidance on when to use this tool versus alternatives like 'search_issues' or 'get_issue_details'. No exclusions 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/eh24905-wiz/jira-mcp'

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