Jira Service Desk ACTION
List Request Types
Lists the customer request types a service desk offers, with the
id, name, and description of each. Call this before Create Request to choose the requestTypeId that matches what the user is asking for: the request type, not the summary wording, decides what kind of ticket gets created. Names vary by desk, so match on meaning rather than assuming a type called "Incident" exists (an IT desk may instead offer "Report a system problem"). Use List Sites for cloudId and List Service Desks for serviceDeskId. Results are paginated automatically up to maxResults. Returns { requestTypes, truncated }, where truncated is true when more types remained unfetched. Example: service desk 1 returns entries such as { "id": "8", "name": "Report a system problem", "description": "Let us know if something isn't working properly", "canCreateRequest": true }. Types with canCreateRequest: false cannot be used to raise a request. Then call List Request Type Fields to see what the chosen type requires. 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 Types 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-types",
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-types",
"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-types",
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 whose request types to list. Use List Service Desks to find valid IDs (e.g. 1). Required |
searchQuery Search Query | string | Filter results to request types matching this text, e.g. hardware. Omit to return every type the desk offers. Optional |
groupId Group ID | integer | Filter results to a single request type group. Group IDs appear as groupIds on the request types returned by this action. Optional |
restrictionStatus Restriction Status | string | Filter by whether the request type is open to all customers or restricted. Optional |
includeHiddenRequestTypesInSearch Include Hidden Request Types In Search | boolean | Whether to include hidden request types. Only applies together with searchQuery. Optional |
maxResults Max Results | integer | Maximum number of items to return across all pages (1-1000). Optional |
expand Expand | string[] | Extra data to include on each request type. Pass ["field"] to return the type's fields inline, which saves a follow-up List Request Type Fields call. field 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-types
- Version
- 0.0.6
- App
- Jira Service Desk
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗