Skip to main content
Glama
vparlapalli490

ServiceNow MCP Server

update_workflow_activity

Modify workflow activities in ServiceNow by updating names, descriptions, or attributes to maintain process accuracy and efficiency.

Instructions

Update an existing activity in a workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activity_idYesActivity ID or sys_id
nameNoName of the activity
descriptionNoDescription of the activity
attributesNoAdditional attributes for the activity

Implementation Reference

  • The core handler function that executes the tool logic: unwraps parameters, prepares the PATCH request to /api/now/table/wf_activity/{activity_id}, and returns the updated activity or error.
    def update_workflow_activity(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        Update an existing activity in a workflow.
        
        Args:
            auth_manager: Authentication manager
            server_config: Server configuration
            params: Parameters for updating a workflow activity
            
        Returns:
            Dict[str, Any]: Updated workflow activity details
        """
        # Unwrap parameters if needed
        params = _unwrap_params(params, UpdateWorkflowActivityParams)
        
        # 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"}
        
        # Prepare data for the API request
        data = {}
        
        if params.get("name"):
            data["name"] = params["name"]
        
        if params.get("description") is not None:
            data["description"] = params["description"]
        
        if params.get("attributes"):
            # Add any additional attributes
            data.update(params["attributes"])
        
        if not data:
            return {"error": "No update parameters provided"}
        
        # 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.patch(url, headers=headers, json=data)
            response.raise_for_status()
            
            result = response.json()
            return {
                "activity": result.get("result", {}),
                "message": "Activity updated successfully",
            }
        except requests.RequestException as e:
            logger.error(f"Error updating workflow activity: {e}")
            return {"error": str(e)}
        except Exception as e:
            logger.error(f"Unexpected error updating workflow activity: {e}")
            return {"error": str(e)}
  • Pydantic BaseModel defining the input schema for the tool, including required activity_id and optional fields for updates.
    class UpdateWorkflowActivityParams(BaseModel):
        """Parameters for updating a workflow activity."""
        
        activity_id: str = Field(..., description="Activity ID or sys_id")
        name: Optional[str] = Field(None, description="Name of the activity")
        description: Optional[str] = Field(None, description="Description of the activity")
        attributes: Optional[Dict[str, Any]] = Field(None, description="Additional attributes for the activity")
  • Registers the 'update_workflow_activity' tool in the central tool_definitions dictionary, specifying the handler function, params schema, description, and serialization method.
    "update_workflow_activity": (
        update_workflow_activity_tool,
        UpdateWorkflowActivityParams,
        str,  # Expects JSON string
        "Update an existing activity in a workflow",
        "json_dict",  # Tool returns Pydantic model
    ),
  • Imports the update_workflow_activity function into the tools package namespace, making it available for further registration.
    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,
    )
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 but offers minimal information. It states this is an update operation (implying mutation) but doesn't address permission requirements, whether changes are reversible, what happens to unspecified fields, or error conditions. This 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 wasted words. It's appropriately sized and front-loaded with the essential information about what the tool does.

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 insufficiently complete. It doesn't explain what the update operation returns, what permissions are needed, or how it differs from related operations. The context signals indicate this is a non-trivial tool (4 parameters, 1 required) that deserves more comprehensive documentation.

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 schema description coverage is 100%, so the schema already documents all four parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema, making the baseline score of 3 appropriate when the schema does the heavy lifting.

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 ('Update') and target ('an existing activity in a workflow'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'update_workflow' or 'add_workflow_activity', which would be needed for a perfect score.

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 like 'add_workflow_activity' or 'delete_workflow_activity'. There's no mention of prerequisites, constraints, or appropriate contexts for this update operation.

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