Skip to main content
Glama
vparlapalli490

ServiceNow MCP Server

delete_workflow_activity

Remove an activity from a ServiceNow workflow to modify automation processes or eliminate outdated steps.

Instructions

Delete an activity from a workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activity_idYesActivity ID or sys_id

Implementation Reference

  • The handler function that executes the deletion of a workflow activity by sending 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 parameters for the delete_workflow_activity tool, requiring the activity_id.
    class DeleteWorkflowActivityParams(BaseModel):
        """Parameters for deleting a workflow activity."""
        
        activity_id: str = Field(..., description="Activity ID or sys_id")
  • Tool registration in get_tool_definitions() mapping the tool name to its aliased handler function, input schema, return type, description, and serialization method.
    "delete_workflow_activity": (
        delete_workflow_activity_tool,
        DeleteWorkflowActivityParams,
        str,
        "Delete an activity from a workflow",
        "str",  # Tool returns simple message
    ),
  • Import of the handler function with alias used in the tool registration.
    from servicenow_mcp.tools.workflow_tools import (
        delete_workflow_activity as delete_workflow_activity_tool,
    )
  • Re-export of the delete_workflow_activity function from workflow_tools.py in the tools package __init__.
    delete_workflow_activity,
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose if deletion is permanent, requires specific permissions, affects related workflow elements, or has side effects like cascading changes, which is critical for a destructive operation.

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 that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with every word earning its place.

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 destructive tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits (e.g., permanence, permissions), expected outcomes, or error handling, leaving significant gaps in understanding how to use it 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 the parameter 'activity_id' well-documented in the schema as 'Activity ID or sys_id'. The description adds no additional meaning beyond what the schema provides, so it meets the baseline of 3 without compensating value.

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 a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'remove_group_members' or 'delete_script_include' by specifying what makes this deletion unique to workflow activities.

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., needing an existing activity), exclusions, or related tools like 'add_workflow_activity' or 'reorder_workflow_activities' for context.

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