Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

activate_workflow

Activate a ServiceNow workflow by providing its workflow ID to initiate automated business processes and task sequences within the platform.

Instructions

Activate a workflow in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_idYesWorkflow ID or sys_id

Implementation Reference

  • The main handler function that implements the logic for activating a workflow by sending a PATCH request to set the 'active' field to 'true' in the ServiceNow wf_workflow table.
    def activate_workflow(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        Activate a workflow in ServiceNow.
        
        Args:
            auth_manager: Authentication manager
            server_config: Server configuration
            params: Parameters for activating a workflow
            
        Returns:
            Dict[str, Any]: Activated workflow details
        """
        # Unwrap parameters if needed
        params = _unwrap_params(params, ActivateWorkflowParams)
        
        # Get the correct auth_manager and server_config
        try:
            auth_manager, server_config = _get_auth_and_config(auth_manager, server_config)
        except ValueError as e:
            logger.error(f"Error getting auth and config: {e}")
            return {"error": str(e)}
        
        workflow_id = params.get("workflow_id")
        if not workflow_id:
            return {"error": "Workflow ID is required"}
        
        # Prepare data for the API request
        data = {
            "active": "true",
        }
        
        # Make the API request
        try:
            headers = auth_manager.get_headers()
            url = f"{server_config.instance_url}/api/now/table/wf_workflow/{workflow_id}"
            
            response = requests.patch(url, headers=headers, json=data)
            response.raise_for_status()
            
            result = response.json()
            return {
                "workflow": result.get("result", {}),
                "message": "Workflow activated successfully",
            }
        except requests.RequestException as e:
            logger.error(f"Error activating workflow: {e}")
            return {"error": str(e)}
        except Exception as e:
            logger.error(f"Unexpected error activating workflow: {e}")
            return {"error": str(e)}
  • Pydantic BaseModel defining the input schema for the activate_workflow tool, requiring a 'workflow_id' string.
    class ActivateWorkflowParams(BaseModel):
        """Parameters for activating a workflow."""
        
        workflow_id: str = Field(..., description="Workflow ID or sys_id")
  • Explicit registration of the 'activate_workflow' tool in the central tool_definitions dictionary used by the MCP server, specifying the handler function alias, input schema model, return type hint, description, and serialization method.
    "activate_workflow": (
        activate_workflow_tool,
        ActivateWorkflowParams,
        str,
        "Activate a workflow in ServiceNow",
        "str",  # Tool returns simple message
    ),
  • Import of the activate_workflow handler function from workflow_tools.py, aliased as activate_workflow_tool for use in the tool definitions.
    from servicenow_mcp.tools.workflow_tools import (
        activate_workflow as activate_workflow_tool,
    )
  • Import of the ActivateWorkflowParams schema model (among others) from workflow_tools.py for use in tool registration.
    from servicenow_mcp.tools.workflow_tools import (
        ActivateWorkflowParams,
        AddWorkflowActivityParams,
        CreateWorkflowParams,
        DeactivateWorkflowParams,
        DeleteWorkflowActivityParams,
        GetWorkflowActivitiesParams,
        GetWorkflowDetailsParams,
        ListWorkflowsParams,
        ListWorkflowVersionsParams,
        ReorderWorkflowActivitiesParams,
        UpdateWorkflowActivityParams,
        UpdateWorkflowParams,
    )
Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral insight. 'Activate' implies a state change, but it doesn't disclose permissions required, side effects (e.g., enabling automation), error conditions, or what 'activate' entails beyond the basic action. This leaves significant gaps for a mutation tool.

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. It's front-loaded with the core action and resource, making it easy to parse quickly.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavior, outcomes, error handling, and usage context, leaving the agent with insufficient information to invoke it reliably beyond the basic parameter.

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?

Schema description coverage is 100%, with the parameter 'workflow_id' documented as 'Workflow ID or sys_id'. The description adds no additional parameter semantics beyond this, so it meets the baseline of 3 where the schema does the heavy lifting.

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

Purpose3/5

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

The description states the verb ('Activate') and resource ('a workflow in ServiceNow'), providing a basic purpose. However, it lacks specificity about what 'activate' means operationally and doesn't distinguish from sibling tools like 'deactivate_workflow' or 'create_workflow' beyond the obvious verb difference.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., workflow must exist, be in a deactivated state), exclusions, or relationships with sibling tools like 'deactivate_workflow' or 'update_workflow'.

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/javerthl/servicenow-mcp'

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