[BUG] Atlassian MCP: `getJiraIssueRemoteIssueLinks` fails with structuredContent type mismatch

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

The getJiraIssueRemoteIssueLinks tool always fails with an MCP validation error. The Jira API returns a JSON array for remote links, but the MCP tool schema expects a JSON object (record), causing a hard crash on every invocation.

What Should Happen?

The tool should return the list of remote links (including linked Confluence pages) for the given Jira issue without error.

Error Messages/Logs

MCP error -32602: MCP error -32602: Invalid tools/call result: [
  {
    "expected": "record",
    "code": "invalid_type",
    "path": ["structuredContent"],
    "message": "Invalid input: expected record, received array"
  }

Steps to Reproduce

1. Have the Atlassian MCP plugin configured and connected to a Jira instance
2. Call getJiraIssueRemoteIssueLinks on any valid Jira issue key
3. Observe the error

Tool: getJiraIssueRemoteIssueLinks
Parameters: { cloudId: "<valid-cloud-id>", issueIdOrKey: "<jira-issue-key>" }

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.56 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Root Cause Analysis

The Jira REST API endpoint GET /rest/api/3/issue/{issueIdOrKey}/remotelink returns a JSON array ([]). The MCP tool's response schema for structuredContent expects a JSON object / record ({}). This type mismatch causes Zod (or equivalent schema validator) to reject the response on every call.

The fix should update the structuredContent schema for this tool to accept an array, or wrap the array in an object (e.g. { remoteLinks: [...] }).

Impact

• Remote links between Jira issues and Confluence pages are completely inaccessible via MCP
• The "Confluence pages" link panel on Jira issues cannot be read
• Workaround: manually extract Confluence page URLs from issue description text and fetch pages individually via getConfluencePage

Environment

• Tool: Claude Code with Atlassian MCP plugin
• Jira site: atoss.atlassian.net (Jira Cloud)
• Affected tool: getJiraIssueRemoteIssueLinks
• Unaffected tools: getJiraIssue (with issuelinks field), getConfluencePage — both work correctly

Related Issues

• anthropics/claude-code #20983 — mentions getJiraIssueRemoteIssueLinks tool name length (closed as duplicate)
• anthropics/claude-code #1919 — similar structuredContent payload issue on updateConfluencePage
• sooperset/mcp-atlassian #714 — general MCP Atlassian structuredContent validation failures