Skip to main content
Glama
echelon-ai-labs

ServiceNow MCP Server

update_workflow_activity

Modify workflow activities in ServiceNow by updating their name, description, or attributes using the specified activity ID through the MCP server.

Instructions

Update an existing activity in a workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Implementation Reference

  • The main execution function for the 'update_workflow_activity' tool. It handles input parameters, makes a PATCH request to the ServiceNow wf_activity table API, and returns the updated activity details 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/parameters for the update_workflow_activity tool, including activity_id (required), name, description, and attributes.
    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")
  • Tool registration entry in the central get_tool_definitions() function's dictionary. Maps the tool name to its handler function alias, input schema, return type hint, 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
    ),
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. It states this is an update operation (implying mutation) but doesn't describe what 'update' entails—whether it overwrites or merges fields, if changes are reversible, what permissions are needed, or what happens on success/failure. For a mutation tool with zero annotation coverage, this leaves critical behavioral aspects unspecified.

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, direct sentence with zero wasted words. It front-loads the core action and target efficiently, making it easy to parse. Every word earns its place by conveying essential purpose.

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 complexity (a mutation tool with nested parameters) and the lack of annotations, schema descriptions (0% coverage), and output schema, the description is incomplete. It doesn't explain what can be updated, how updates behave, or what the tool returns, leaving significant gaps for an AI agent to infer correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides no information about parameters, and the schema description coverage is 0% (no descriptions in the schema). With 1 required parameter ('params') that contains nested properties (activity_id, name, description, attributes), the description fails to compensate for the complete lack of schema documentation, leaving all parameter meanings unclear.

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'), making the purpose immediately understandable. It distinguishes itself from siblings like 'add_workflow_activity' (create) and 'delete_workflow_activity' (remove), though it doesn't explicitly contrast with 'update_workflow' (which modifies the workflow itself rather than 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 ID), constraints (e.g., permissions required), or when to choose this over similar tools like 'reorder_workflow_activities' or 'update_workflow'. The description assumes context without providing it.

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

Related 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/echelon-ai-labs/servicenow-mcp'

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