Skip to main content
Glama

resumeWorkflow

Resume suspended workflow instances in Adobe Experience Manager to continue automated content management processes.

Instructions

Resume a suspended workflow instance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowIdYes

Implementation Reference

  • Core handler function that executes the resume workflow logic by sending a POST request to the AEM workflow instance endpoint with action 'resume'.
    async resumeWorkflow(workflowId: string): Promise<{
      success: boolean;
      operation: string;
      timestamp: string;
      data: {
        workflowId: string;
        status: string;
        resumedAt: string;
      };
    }> {
      return safeExecute(async () => {
        if (!workflowId) {
          throw createAEMError(
            AEM_ERROR_CODES.INVALID_PARAMETERS, 
            'Workflow ID is required', 
            { workflowId }
          );
        }
    
        // Resume the workflow
        const resumeData = {
          action: 'resume'
        };
    
        const response = await this.httpClient.post(
          `/etc/workflow/instances/${workflowId}`, 
          resumeData,
          {
            headers: {
              'Content-Type': 'application/json'
            }
          }
        );
    
        return createSuccessResponse({
          workflowId,
          status: 'RUNNING',
          resumedAt: new Date().toISOString()
        }, 'resumeWorkflow');
      }, 'resumeWorkflow');
    }
  • MCP tool handler case that extracts workflowId from arguments and delegates to aemConnector.resumeWorkflow.
    case 'resumeWorkflow': {
      const workflowId = (args as { workflowId: string }).workflowId;
      const result = await aemConnector.resumeWorkflow(workflowId);
      return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
    }
  • Input schema definition for the resumeWorkflow tool, requiring workflowId string.
    {
      name: 'resumeWorkflow',
      description: 'Resume a suspended workflow instance',
      inputSchema: {
        type: 'object',
        properties: {
          workflowId: { type: 'string' }
        },
        required: ['workflowId'],
      },
    },
  • Secondary handler in MCPRequestHandler that delegates to aemConnector.resumeWorkflow.
    case 'resumeWorkflow':
      return await this.aemConnector.resumeWorkflow(params.workflowId);
  • Tool description and parameters listed in available methods.
    { name: 'resumeWorkflow', description: 'Resume a suspended workflow instance', parameters: ['workflowId'] },
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 states the action ('Resume') but doesn't disclose critical traits such as whether this requires specific permissions, if it's idempotent, what happens on success/failure, or any rate limits. For a mutation tool (implied by 'Resume') with zero annotation coverage, this is a significant gap in transparency beyond the basic action.

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, efficient sentence ('Resume a suspended workflow instance') that is front-loaded with the core action and resource. There is zero waste or redundancy, making it highly concise and well-structured for quick understanding.

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 (a mutation operation with no annotations, no output schema, and 1 undocumented parameter), the description is incomplete. It lacks details on behavioral traits, parameter semantics, expected outcomes, or error handling. While concise, it doesn't provide enough context for safe and effective use by an AI agent, especially compared to more comprehensive sibling tools in the list.

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

Parameters3/5

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

The input schema has 1 parameter with 0% description coverage, so the schema provides no semantic context. The description adds no information about the 'workflowId' parameter, such as its format, source, or constraints. However, with only one parameter, the baseline is higher; the description implies the parameter identifies a suspended workflow instance but doesn't elaborate, resulting in minimal added value beyond the schema's structural definition.

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 'Resume a suspended workflow instance' clearly states the verb ('Resume') and resource ('a suspended workflow instance'), making the purpose immediately understandable. It distinguishes from siblings like 'startWorkflow', 'cancelWorkflow', and 'suspendWorkflow' by specifying it acts on already-suspended instances. However, it doesn't explicitly contrast with 'completeWorkflowStep' or 'listActiveWorkflows', which slightly limits differentiation.

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

Usage Guidelines3/5

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

The description implies usage by indicating it resumes 'suspended' workflows, suggesting it should be used when a workflow is in a suspended state. However, it doesn't provide explicit guidance on when to use this versus alternatives like 'cancelWorkflow' or 'startWorkflow', nor does it mention prerequisites (e.g., needing a valid workflow ID from 'listActiveWorkflows' or 'suspendWorkflow'). The context is clear but lacks detailed exclusions or named alternatives.

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