Skip to main content
Glama
vparlapalli490

ServiceNow MCP Server

reorder_workflow_activities

Change the sequence of activities in a ServiceNow workflow by specifying the new order of activity IDs for a given workflow ID.

Instructions

Reorder activities in a workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_idYesWorkflow ID or sys_id
activity_idsYesList of activity IDs in the desired order

Implementation Reference

  • The core handler function that executes the tool logic. It unwraps parameters using ReorderWorkflowActivitiesParams, authenticates, and iteratively PATCHes the 'order' field on each wf_activity record via the ServiceNow REST API to achieve reordering.
    def reorder_workflow_activities(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        Reorder activities in a workflow.
        
        Args:
            auth_manager: Authentication manager
            server_config: Server configuration
            params: Parameters for reordering workflow activities
            
        Returns:
            Dict[str, Any]: Result of the reordering operation
        """
        # Unwrap parameters if needed
        params = _unwrap_params(params, ReorderWorkflowActivitiesParams)
        
        # 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"}
        
        activity_ids = params.get("activity_ids")
        if not activity_ids:
            return {"error": "Activity IDs are required"}
        
        # Make the API requests to update the order of each activity
        try:
            headers = auth_manager.get_headers()
            results = []
            
            for i, activity_id in enumerate(activity_ids):
                # Calculate the new order value (100, 200, 300, etc.)
                new_order = (i + 1) * 100
                
                url = f"{server_config.instance_url}/api/now/table/wf_activity/{activity_id}"
                data = {"order": new_order}
                
                try:
                    response = requests.patch(url, headers=headers, json=data)
                    response.raise_for_status()
                    
                    results.append({
                        "activity_id": activity_id,
                        "new_order": new_order,
                        "success": True,
                    })
                except requests.RequestException as e:
                    logger.error(f"Error updating activity order: {e}")
                    results.append({
                        "activity_id": activity_id,
                        "error": str(e),
                        "success": False,
                    })
            
            return {
                "message": "Activities reordered",
                "workflow_id": workflow_id,
                "results": results,
            }
        except Exception as e:
            logger.error(f"Unexpected error reordering workflow activities: {e}")
            return {"error": str(e)}
  • Pydantic BaseModel defining the input schema for the tool, validating workflow_id (str) and activity_ids (list of str). Used for parameter unwrapping and validation.
    class ReorderWorkflowActivitiesParams(BaseModel):
        """Parameters for reordering workflow activities."""
        
        workflow_id: str = Field(..., description="Workflow ID or sys_id")
        activity_ids: List[str] = Field(..., description="List of activity IDs in the desired order")
  • MCP tool registration in the central tool_definitions dictionary. Maps tool name to (handler function alias, params schema, return type, description, serialization method). This is used by the MCP server to expose the tool.
    "reorder_workflow_activities": (
        reorder_workflow_activities_tool,
        ReorderWorkflowActivitiesParams,
        str,
        "Reorder activities in a workflow",
        "str",  # Tool returns simple message
    ),
  • Import of the handler function aliased as reorder_workflow_activities_tool for use in tool registration.
    from servicenow_mcp.tools.workflow_tools import (
        reorder_workflow_activities as reorder_workflow_activities_tool,
  • Re-export of the handler from workflow_tools.py in the tools package __init__, making it available for imports in tool_utils.py.
    reorder_workflow_activities,
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Reorder' implies a mutation operation, but the description doesn't disclose critical behavioral traits: whether this requires specific permissions, if it's destructive (overwrites existing order), what happens on success/failure, or any rate limits. It adds no context beyond the basic action, which is inadequate for a mutation tool with zero annotation coverage.

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 with zero waste. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place, and there's no redundant or verbose phrasing.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks behavioral context (permissions, effects), usage guidance, and any indication of return values or errors. For a tool that modifies workflow state, this minimal description leaves significant gaps for an agent to operate safely and effectively.

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 clear descriptions for both parameters (workflow_id and activity_ids). The description adds no additional meaning beyond what the schema provides (e.g., it doesn't explain format constraints or ordering semantics). Baseline 3 is appropriate when the schema does the heavy lifting, though the description could have clarified that activity_ids must be a complete list in new order.

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 'Reorder activities in a workflow' clearly states the action (reorder) and resource (activities in a workflow). It distinguishes from siblings like 'add_workflow_activity' or 'delete_workflow_activity' by specifying reordering rather than adding/removing. However, it doesn't explicitly mention that it's for changing the sequence/order of existing activities, which could be slightly more specific.

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. It doesn't mention prerequisites (e.g., needing an existing workflow with activities), when not to use it, or how it relates to siblings like 'update_workflow_activity' or 'get_workflow_activities'. This leaves the agent to infer usage from the name alone.

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/vparlapalli490/MCP'

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