Jira Service Desk ACTION
List Issue Attachments
List metadata for every attachment on a Jira Service Desk request.
issueIdOrKey accepts either a Jira issue key (e.g. IT-42) or a numeric Jira issue ID (e.g. 10001). Results are paginated automatically up to maxResults. Returns { attachments, truncated }, where each attachment includes id, filename, size (bytes), mimeType, and content (an opaque reference URL whose exact shape varies by account access level and is not directly fetchable through this connection's authentication), and truncated is true when more attachments remained unfetched. Use Download Issue Attachment with an attachment id and the same issueIdOrKey to fetch the binary content — do not call content directly. If this connection has customer-level access rather than agent access, only public attachments are returned; internal attachments exist but won't appear here. Returns { attachments: [], truncated: false } (no error) when the request exists but has no visible attachments. Example: issue IT-42 with one attachment returns { "attachments": [{ "id": "10042", "filename": "screenshot.png", "size": 84213, "mimeType": "image/png", "content": "<opaque reference URL>" }], "truncated": false }. See the documentation- Action
- Read only
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Jira Service Desk account once, then configure and run List Issue Attachments from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "jira_service_desk-list-issue-attachments",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
jira_service_desk: { authProvisionId: "apn_xxxxxxx" },
cloudId: "Cloud ID",
issueIdOrKey: "Issue ID or Key",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "jira_service_desk-list-issue-attachments",
"configured_props": {
"jira_service_desk": { "authProvisionId": "apn_xxxxxxx" },
"cloudId": "Cloud ID",
"issueIdOrKey": "Issue ID or Key"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "jira_service_desk",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "jira_service_desk-list-issue-attachments",
arguments: {
cloudId: "Cloud ID",
issueIdOrKey: "Issue ID or Key",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
cloudId Cloud ID | string | The Atlassian site (cloud) ID, e.g. 822faf0d-5427-420e-9016-999d3dc76918. Run List Sites to get the id of every site you can access. Required |
issueIdOrKey Issue ID or Key | string | The ID or key of the Jira Service Desk request (e.g. IT-42 or 10001). Use List My Requests to find the issueKey of a request (in its requests array). Required |
maxResults Max Results | integer | Maximum number of items to return across all pages (1-1000). Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- jira_service_desk-list-issue-attachments
- Version
- 0.0.4
- App
- Jira Service Desk
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗