Jira Service Desk ACTION
List Request Type Fields
Lists the fields a given request type accepts, so you can build the
additionalFieldValues argument for Create Request in a single pass. Each entry gives the fieldId to use as the key, whether it is required, its jiraSchema (the value format), and any validValues for select-style fields. Use List Sites for cloudId, List Service Desks for serviceDeskId, and List Request Types for requestTypeId. Example: request type 4 ("Onboard new employees") on service desk 1 returns a required summary plus optional duedate (jiraSchema.type date, so pass "2026-09-01"), description, and attachment. Also returns canRaiseOnBehalfOf and canAddRequestParticipants, which tell you whether the raiseOnBehalfOf and requestParticipants arguments of Create Request are usable with this account. Hidden fields are only visible to service desk administrators. 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 Request Type Fields 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-request-type-fields",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
jira_service_desk: { authProvisionId: "apn_xxxxxxx" },
cloudId: "Cloud ID",
serviceDeskId: "Service Desk ID",
},
})
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-request-type-fields",
"configured_props": {
"jira_service_desk": { "authProvisionId": "apn_xxxxxxx" },
"cloudId": "Cloud ID",
"serviceDeskId": "Service Desk ID"
}
}'// 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-request-type-fields",
arguments: {
cloudId: "Cloud ID",
serviceDeskId: "Service Desk ID",
},
})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 |
serviceDeskId Service Desk ID | string | The service desk the request type belongs to. Use List Service Desks to find valid IDs (e.g. 1). Required |
requestTypeId Request Type ID | string | The request type whose fields to list. Use List Request Types to find valid IDs (e.g. 4). Required |
expand Expand | string[] | Extra data to include. Pass ["hiddenFields"] to also return fields hidden on the request type, which only a service desk administrator can see. hiddenFields is the only value this endpoint accepts. 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-request-type-fields
- Version
- 0.0.6
- App
- Jira Service Desk
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗