Skip to main content
Glama
akhilthomas236

MCP Jira & Confluence Server

get-my-assigned-issues

Retrieve your assigned Jira issues sorted by priority and creation date. Optionally limit results or include completed tasks.

Instructions

Get issues assigned to the current user, ordered by priority (highest first) and creation date (newest first)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_resultsNoMaximum number of issues to return (default: 25, max: 100)
include_doneNoInclude completed/closed issues (default: false)

Implementation Reference

  • Tool 'get-my-assigned-issues' is registered in the list_tools handler with its input schema (max_results, include_done).
    types.Tool(
        name="get-my-assigned-issues",
        description="Get issues assigned to the current user, ordered by priority (highest first) and creation date (newest first)",
        inputSchema={
            "type": "object",
            "properties": {
                "max_results": {
                    "type": "integer", 
                    "description": "Maximum number of issues to return (default: 25, max: 100)",
                    "default": 25
                },
                "include_done": {
                    "type": "boolean",
                    "description": "Include completed/closed issues (default: false)",
                    "default": False
                },
            },
            "required": [],
        },
    ),
  • Input schema for get-my-assigned-issues: max_results (integer, default 25, max 100) and include_done (boolean, default false).
    inputSchema={
        "type": "object",
        "properties": {
            "max_results": {
                "type": "integer", 
                "description": "Maximum number of issues to return (default: 25, max: 100)",
                "default": 25
            },
            "include_done": {
                "type": "boolean",
                "description": "Include completed/closed issues (default: false)",
                "default": False
            },
        },
        "required": [],
    },
  • Tool execution handler for 'get-my-assigned-issues' - calls jira_client.get_my_assigned_issues() and formats the response with issue details (key, summary, status, priority, type, created, due date).
    elif name == "get-my-assigned-issues":
        max_results = arguments.get("max_results", 25)
        include_done = arguments.get("include_done", False)
        
        # Validate max_results
        if max_results > 100:
            max_results = 100
        elif max_results < 1:
            max_results = 25
            
        result = await jira_client.get_my_assigned_issues(
            max_results=max_results,
            include_done=include_done
        )
        
        issues = result.get("issues", [])
        total = result.get("total", 0)
        
        if not issues:
            return [
                types.TextContent(
                    type="text",
                    text="No issues assigned to you were found.",
                )
            ]
        
        # Format the response
        response_text = f"Found {len(issues)} out of {total} issues assigned to you:\n\n"
        
        for issue in issues:
            fields = issue.get("fields", {})
            key = issue.get("key", "Unknown")
            summary = fields.get("summary", "No summary")
            status = fields.get("status", {}).get("name", "Unknown")
            priority = fields.get("priority", {}).get("name", "Unknown")
            created = fields.get("created", "Unknown")
            due_date = fields.get("duedate", "No due date")
            issue_type = fields.get("issuetype", {}).get("name", "Unknown")
            
            # Format dates nicely
            if created != "Unknown":
                try:
                    from datetime import datetime
                    created_dt = datetime.fromisoformat(created.replace('Z', '+00:00'))
                    created = created_dt.strftime("%Y-%m-%d %H:%M")
                except:
                    pass
            
            response_text += f"**{key}**: {summary}\n"
            response_text += f"  - Status: {status}\n"
            response_text += f"  - Priority: {priority}\n"
            response_text += f"  - Type: {issue_type}\n"
            response_text += f"  - Created: {created}\n"
            response_text += f"  - Due Date: {due_date}\n\n"
        
        return [
            types.TextContent(
                type="text",
                text=response_text,
            ),
            types.EmbeddedResource(
                type="resource",
                resource=types.TextResourceContents(
                    uri=AnyUrl("jira://my-assigned-issues"),
                    text=response_text,
                    mimeType="text/markdown"
                )
            )
        ]
  • JiraClient.get_my_assigned_issues() - builds a JQL query filtering by currentUser() assignee, optionally excluding done/closed/resolved issues, ordered by priority DESC and created DESC.
    async def get_my_assigned_issues(self, max_results: int = 50, include_done: bool = False) -> Dict[str, Any]:
        """Get issues assigned to the current user, ordered by priority and date."""
        # Build JQL query for assigned issues
        jql_parts = ["assignee = currentUser()"]
        
        if not include_done:
            jql_parts.append('status not in ("Done", "Closed", "Resolved")')
        
        # Order by priority (highest first), then by created date (newest first)
        jql = " AND ".join(jql_parts) + " ORDER BY priority DESC, created DESC"
        
        fields = "summary,description,status,assignee,reporter,labels,priority,created,updated,issuetype,duedate"
        return await self.get("search", params={
            "jql": jql,
            "startAt": 0,
            "maxResults": max_results,
            "fields": fields
        })
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds ordering behavior (priority then creation date) which is useful, but does not mention that this is a read-only operation, authentication requirements, or pagination behavior beyond max_results.

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 sentence that is front-loaded with the core purpose and ordering details. Every word adds value, with no redundant or unnecessary information.

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?

The description covers purpose and ordering, but lacks information about the return format or content of each issue (e.g., fields returned). Since there is no output schema, the description could have compensated by mentioning what keys/values are returned.

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?

Input schema coverage is 100%, so the baseline is 3. The description does not add any information about the two parameters (max_results, include_done) that is not already in the schema.

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?

The description clearly states the tool retrieves issues assigned to the current user, with specific ordering by priority and creation date. This distinguishes it from sibling tools like get-jira-issue, which retrieves a single issue.

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 when a user needs their assigned issues, but provides no explicit guidance on when not to use it or alternatives. Since sibling tools include search-confluence and get-jira-issue, the description could mention that this tool is for the current user's assignments only.

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/akhilthomas236/mcp-jira-confluence-sse'

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