Skip to main content
Glama
marco-looy

Pega DX MCP Server

by marco-looy
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

perform_bulk_action

Apply a case action to multiple cases in one operation. Works with case-wide actions only, synchronously in Infinity or asynchronously in Launchpad.

Instructions

Perform case action on multiple cases simultaneously (bulk operation). Executes the specified action on all cases provided in the request. In Infinity, actions are performed synchronously. In Launchpad, actions are performed asynchronously in the background. NOTE: Only supports case-wide actions that update cases directly - assignment-level actions like Transfer and Adjust Assignment SLA are not supported.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionIDYesAction ID for case/stage action (Example: "pyUpdateCaseDetails", "pyApproval"). CRITICAL: Action IDs are CASE-SENSITIVE and have no spaces even if display names do ("Edit details" → "pyUpdateCaseDetails"). Use get_case to find correct ID from availableActions array - use "ID" field not "name" field. This action must be a case-wide action that updates cases directly.
casesYesArray of case objects to perform the action on. Each case object must contain an ID property with the full case handle.
runningModeNoExecution mode for Launchpad only. "async" schedules the action to be performed in the background rather than immediately. Not applicable for Infinity which always executes synchronously. Note: As of Launchpad 4.3, there is no way to check the status of asynchronous bulk action processing.
contentNoA map of scalar properties and embedded page properties to be set during action execution. Same format as single case action content.
pageInstructionsNoOptional list of page-related operations for embedded pages, page lists, or page groups. Required for setting embedded page references.
attachmentsNoA list of attachments to be added to specific attachment fields during action execution.
sessionCredentialsNoOptional session-specific credentials. If not provided, uses environment variables. Supports two authentication modes: (1) OAuth mode - provide baseUrl, clientId, and clientSecret, or (2) Token mode - provide baseUrl and accessToken.

Tool Definition Quality

A4.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It clearly explains synchronous vs asynchronous behavior, action ID case sensitivity and space rules, and explicitly lists unsupported action types. Does not describe return value or error behavior, but given complexity, this is adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is lengthy but well-structured with clear sections. It is front-loaded with main purpose and behavior. Every sentence adds value, but could be slightly more concise without losing information.

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

Completeness5/5

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

Given the tool's complexity (7 parameters, nested objects, async/sync modes, platform differences), the description covers all aspects including limitations and best practices. No output schema, but behavior is sufficiently explained.

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

Parameters5/5

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

Schema coverage is 100%, but description adds substantial value: explains actionID case sensitivity and example, integration with get_case; explains runningMode limitations; provides detailed pageInstructions with examples; describes sessionCredentials auth modes. This goes beyond schema to enhance understanding.

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

Purpose5/5

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

The description clearly states the tool performs a case action on multiple cases simultaneously. It uses specific verb 'Perform' and resource 'case action on multiple cases', and distinguishes from sibling tools like 'perform_case_action' (single case) and 'bulk_cases_patch' (different operation).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use (bulk operation on multiple cases) and when not (assignment-level actions like Transfer are not supported). Provides context on synchronous vs asynchronous behavior for Infinity vs Launchpad. Also directs to use get_case to find correct action ID.

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/marco-looy/pega-dx-mcp'

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