Skip to main content
Glama

listActiveWorkflows

Monitor and manage currently running workflow instances in Adobe Experience Manager to track progress and identify bottlenecks.

Instructions

List all currently running workflow instances

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Implementation Reference

  • MCP server dispatch handler for listActiveWorkflows tool, extracts limit and calls AEMConnector
    case 'listActiveWorkflows': {
        const limit = args.limit;
        const result = await aemConnector.listActiveWorkflows(limit);
        return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
  • Delegation from AEMConnector to WorkflowOperations
    async listActiveWorkflows(limit) {
        return this.workflowOps.listActiveWorkflows(limit);
  • Core handler logic: Queries AEM QueryBuilder for running cq:WorkflowInstance nodes and maps to response format
    async listActiveWorkflows(limit = 20) {
        return safeExecute(async () => {
            try {
                // Query active workflows
                const response = await this.httpClient.get('/bin/querybuilder.json', {
                    params: {
                        type: 'cq:WorkflowInstance',
                        'property': 'state',
                        'property.value': 'RUNNING',
                        'p.limit': limit.toString(),
                        'p.hits': 'full'
                    }
                });
                const workflows = (response.data.hits || []).map((hit) => ({
                    workflowId: hit.path?.split('/').pop() || hit.name,
                    model: hit['jcr:content/model'] || hit.model,
                    payloadPath: hit['jcr:content/payload'] || hit.payload,
                    status: hit['jcr:content/state'] || hit.state,
                    startedBy: hit['jcr:content/startedBy'] || hit.startedBy,
                    startedAt: hit['jcr:content/startedAt'] || hit.startedAt,
                    currentStep: hit['jcr:content/currentStep'] || hit.currentStep,
                    progress: this.calculateProgressFromHit(hit)
                }));
                return createSuccessResponse({
                    workflows,
                    totalCount: workflows.length,
                    activeCount: workflows.length,
                    completedCount: 0,
                    failedCount: 0
                }, 'listActiveWorkflows');
            }
            catch (error) {
                throw handleAEMHttpError(error, 'listActiveWorkflows');
            }
        }, 'listActiveWorkflows');
  • Input schema and metadata for the MCP tool listActiveWorkflows
    {
        name: 'listActiveWorkflows',
        description: 'List all currently running workflow instances',
        inputSchema: {
            type: 'object',
            properties: {
                limit: { type: 'number' }
            }
        },
    },
  • Registration of tools list handler, which includes listActiveWorkflows schema
    server.setRequestHandler(ListToolsRequestSchema, async () => {
        return { tools };
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'currently running' instances, implying real-time status, but doesn't cover critical aspects like pagination (via the 'limit' parameter), response format, error handling, or authentication needs. This leaves significant gaps for a tool that likely returns dynamic data.

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

Conciseness5/5

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

The description is a single, clear sentence with no wasted words, making it highly concise and front-loaded. It efficiently communicates the core purpose without unnecessary elaboration.

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

Completeness2/5

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

Given the tool's complexity (listing dynamic workflow instances), lack of annotations, 0% schema coverage, and no output schema, the description is insufficient. It doesn't explain what 'currently running' entails, how results are structured, or how to handle the 'limit' parameter, leaving the agent with inadequate information for reliable use.

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

Parameters2/5

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

The input schema has 1 parameter ('limit') with 0% description coverage, and the tool description provides no information about parameters. Since the schema doesn't explain what 'limit' does (e.g., pagination or max results), the description fails to compensate, leaving the parameter's meaning unclear.

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

Purpose4/5

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

The description clearly states the verb ('List') and resource ('currently running workflow instances'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'getWorkflowModels' or 'startWorkflow', which prevents a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'getWorkflowModels' (which might list workflow definitions) or 'startWorkflow' (which initiates workflows). It lacks context about prerequisites or exclusions, offering only a basic statement of function.

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/indrasishbanerjee/aem-mcp-server'

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