Skip to main content
Glama
yuezheng2006

Personal JIRA MCP

by yuezheng2006

get_issue_attachment

Retrieve specific attachments from JIRA issues by providing the issue key and attachment ID, enabling access to files and documents linked to work items.

Instructions

获取JIRA问题附件

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_keyYes
attachment_idYes

Implementation Reference

  • The handler function for the 'get_issue_attachment' tool, decorated with @mcp.tool for registration in the FastMCP server. It retrieves a specific attachment by ID from a JIRA issue, downloads the content, and returns it as base64-encoded string (for images/binary) or plain text (for text files), along with metadata.
    @mcp.tool(
        description="获取JIRA问题附件",
    )
    def get_issue_attachment(
        issue_key: str,
        attachment_id: str,
    ) -> Dict[str, Any]:
        """获取JIRA问题附件内容.
        
        Args:
            issue_key: JIRA问题键
            attachment_id: 附件ID
        
        Returns:
            Dict[str, Any]: 附件内容
        """
        logger.info(f"获取问题附件: issue={issue_key}, attachment_id={attachment_id}")
        try:
            client = get_jira_client()
            issue = client.issue(issue_key)
            
            # 查找指定ID的附件
            attachment = None
            
            # 检查attachments字段
            attachments = []
            if hasattr(issue.fields, "attachments") and issue.fields.attachments:
                attachments = issue.fields.attachments
            elif hasattr(issue.fields, "attachment") and issue.fields.attachment:
                attachments = issue.fields.attachment
                
            for att in attachments:
                if att.id == attachment_id:
                    attachment = att
                    break
            
            if not attachment:
                return {"error": f"未找到ID为 {attachment_id} 的附件"}
            
            # 获取附件内容
            content = attachment.get()
            
            # 确定返回类型:对于图片类型,返回Base64编码;对于文本类型,返回文本内容
            mime_type = attachment.mimeType
            filename = attachment.filename
            
            result = {
                "id": attachment.id,
                "filename": filename,
                "size": attachment.size,
                "content_type": mime_type,
                "created": attachment.created,
            }
            
            # 处理不同的内容类型
            if mime_type.startswith("image/"):
                # 对于图片,返回Base64编码
                result["content"] = base64.b64encode(content).decode('utf-8')
                result["encoding"] = "base64"
            elif mime_type.startswith("text/"):
                # 对于文本文件,直接返回文本内容
                try:
                    result["content"] = content.decode('utf-8')
                    result["encoding"] = "text"
                except UnicodeDecodeError:
                    # 如果解码失败,回退到Base64
                    result["content"] = base64.b64encode(content).decode('utf-8')
                    result["encoding"] = "base64"
            else:
                # 对于其他类型,返回Base64编码
                result["content"] = base64.b64encode(content).decode('utf-8')
                result["encoding"] = "base64"
            
            return result
        except Exception as e:
            logger.error(f"获取问题 {issue_key} 的附件 {attachment_id} 失败: {str(e)}")
            return {"error": str(e)}
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 implies a read operation ('get'), but doesn't disclose behavioral traits such as authentication needs, rate limits, error handling, or what the output looks like (e.g., file content or metadata). For a tool with no annotation coverage, this is a significant gap.

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 in Chinese ('获取JIRA问题附件'), which is appropriately sized and front-loaded. There's no wasted text, making it highly concise and well-structured for its purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (2 required parameters, no annotations, no output schema), the description is incomplete. It lacks details on usage context, parameter meanings, behavioral aspects, and output format, making it inadequate for an AI agent to reliably invoke the tool without additional context.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It mentions 'JIRA issue attachment' but doesn't explain the parameters 'issue_key' and 'attachment_id' (e.g., format, examples, or how they relate). The description adds minimal meaning beyond the schema, failing to address the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '获取JIRA问题附件' (Get JIRA issue attachment) states a clear verb ('get') and resource ('JIRA issue attachment'), but it's vague about scope and doesn't distinguish from sibling tools like 'get_issue_attachments' (plural) or 'get_attachment_by_filename'. It specifies what it does but lacks precision about what exactly is retrieved.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'get_issue_attachments' (likely lists attachments) and 'get_attachment_by_filename' (retrieves by filename), the description doesn't indicate that this tool requires specific IDs or is for single attachments, 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/yuezheng2006/mcp-server-jira'

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