Skip to main content
Glama
JLKmach

ServiceNow MCP Server

by JLKmach

delete_workflow_activity

Remove an activity from a ServiceNow workflow to update process automation or correct configuration errors.

Instructions

Delete an activity from a workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activity_idYesActivity ID or sys_id

Implementation Reference

  • The main handler function that implements the logic for deleting a workflow activity by making a DELETE request to the ServiceNow wf_activity table endpoint.
    def delete_workflow_activity(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        Delete an activity from a workflow.
        
        Args:
            auth_manager: Authentication manager
            server_config: Server configuration
            params: Parameters for deleting a workflow activity
            
        Returns:
            Dict[str, Any]: Result of the deletion operation
        """
        # Unwrap parameters if needed
        params = _unwrap_params(params, DeleteWorkflowActivityParams)
        
        # 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)}
        
        activity_id = params.get("activity_id")
        if not activity_id:
            return {"error": "Activity ID is required"}
        
        # Make the API request
        try:
            headers = auth_manager.get_headers()
            url = f"{server_config.instance_url}/api/now/table/wf_activity/{activity_id}"
            
            response = requests.delete(url, headers=headers)
            response.raise_for_status()
            
            return {
                "message": "Activity deleted successfully",
                "activity_id": activity_id,
            }
        except requests.RequestException as e:
            logger.error(f"Error deleting workflow activity: {e}")
            return {"error": str(e)}
        except Exception as e:
            logger.error(f"Unexpected error deleting workflow activity: {e}")
            return {"error": str(e)}
  • Pydantic BaseModel defining the input schema for the delete_workflow_activity tool, requiring an activity_id.
    class DeleteWorkflowActivityParams(BaseModel):
        """Parameters for deleting a workflow activity."""
        
        activity_id: str = Field(..., description="Activity ID or sys_id")
  • Tool registration entry in get_tool_definitions() that maps 'delete_workflow_activity' to its handler, input schema, return type, description, and serialization method for MCP server integration.
    "delete_workflow_activity": (
        delete_workflow_activity_tool,
        DeleteWorkflowActivityParams,
        str,
        "Delete an activity from a workflow",
        "str",  # Tool returns simple message
    ),
  • Export/import of the delete_workflow_activity handler in the tools package __init__.py, making it available for import from the tools module.
    from servicenow_mcp.tools.workflow_tools import (
        activate_workflow,
        add_workflow_activity,
        create_workflow,
        deactivate_workflow,
        delete_workflow_activity,
        get_workflow_activities,
        get_workflow_details,
        list_workflow_versions,
        list_workflows,
        reorder_workflow_activities,
        update_workflow,
        update_workflow_activity,
    )
  • Import alias of the delete_workflow_activity function as delete_workflow_activity_tool used in the tool registration.
    from servicenow_mcp.tools.workflow_tools import (
        delete_workflow_activity as delete_workflow_activity_tool,
    )
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. It states 'Delete' implying a destructive mutation, but fails to disclose behavioral traits such as permissions required, whether deletion is permanent or reversible, or any side effects (e.g., impact on workflow integrity).

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 is front-loaded and appropriately sized for the tool's purpose, 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?

Given the tool's complexity as a destructive operation with no annotations and no output schema, the description is incomplete. It lacks critical context such as success/error responses, confirmation prompts, or dependencies, leaving significant gaps for an AI agent.

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 'activity_id' documented as 'Activity ID or sys_id'. The description adds no additional meaning beyond this, as it does not explain what an 'activity' entails or provide usage examples. Baseline 3 is appropriate given high schema coverage.

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 action ('Delete') and target ('an activity from a workflow'), providing specific verb+resource. However, it does not distinguish from sibling tools like 'delete_script_include' or 'delete_story_dependency', which 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 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. The description lacks context about prerequisites, permissions, or relationships with sibling tools like 'get_workflow_activities' or 'add_workflow_activity', leaving usage unclear.

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

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