Skip to main content
Glama
echelon-ai-labs

ServiceNow MCP Server

update_change_request

Modify details of an existing change request in ServiceNow, including assignment group, category, description, impact, risk, start/end dates, state, and work notes using the Change Id.

Instructions

Update an existing change request in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Implementation Reference

  • The core handler function that executes the update_change_request tool. It validates input parameters using UpdateChangeRequestParams, prepares the update data, and sends a PUT request to the ServiceNow change_request table API endpoint.
    def update_change_request(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        Update an existing change request in ServiceNow.
    
        Args:
            auth_manager: The authentication manager.
            server_config: The server configuration.
            params: The parameters for updating the change request.
    
        Returns:
            The updated change request.
        """
        # Unwrap and validate parameters
        result = _unwrap_and_validate_params(
            params, 
            UpdateChangeRequestParams, 
            required_fields=["change_id"]
        )
        
        if not result["success"]:
            return result
        
        validated_params = result["params"]
        
        # Prepare the request data
        data = {}
        
        # Add fields if provided
        if validated_params.short_description:
            data["short_description"] = validated_params.short_description
        if validated_params.description:
            data["description"] = validated_params.description
        if validated_params.state:
            data["state"] = validated_params.state
        if validated_params.risk:
            data["risk"] = validated_params.risk
        if validated_params.impact:
            data["impact"] = validated_params.impact
        if validated_params.category:
            data["category"] = validated_params.category
        if validated_params.assignment_group:
            data["assignment_group"] = validated_params.assignment_group
        if validated_params.start_date:
            data["start_date"] = validated_params.start_date
        if validated_params.end_date:
            data["end_date"] = validated_params.end_date
        if validated_params.work_notes:
            data["work_notes"] = validated_params.work_notes
        
        # Get the instance URL
        instance_url = _get_instance_url(auth_manager, server_config)
        if not instance_url:
            return {
                "success": False,
                "message": "Cannot find instance_url in either server_config or auth_manager",
            }
        
        # Get the headers
        headers = _get_headers(auth_manager, server_config)
        if not headers:
            return {
                "success": False,
                "message": "Cannot find get_headers method in either auth_manager or server_config",
            }
        
        # Add Content-Type header
        headers["Content-Type"] = "application/json"
        
        # Make the API request
        url = f"{instance_url}/api/now/table/change_request/{validated_params.change_id}"
        
        try:
            response = requests.put(url, json=data, headers=headers)
            response.raise_for_status()
            
            result = response.json()
            
            return {
                "success": True,
                "message": "Change request updated successfully",
                "change_request": result["result"],
            }
        except requests.exceptions.RequestException as e:
            logger.error(f"Error updating change request: {e}")
            return {
                "success": False,
                "message": f"Error updating change request: {str(e)}",
            }
  • Pydantic model defining the input schema for the update_change_request tool, including required change_id and optional fields for updating the change request.
    class UpdateChangeRequestParams(BaseModel):
        """Parameters for updating a change request."""
    
        change_id: str = Field(..., description="Change request ID or sys_id")
        short_description: Optional[str] = Field(None, description="Short description of the change request")
        description: Optional[str] = Field(None, description="Detailed description of the change request")
        state: Optional[str] = Field(None, description="State of the change request")
        risk: Optional[str] = Field(None, description="Risk level of the change")
        impact: Optional[str] = Field(None, description="Impact of the change")
        category: Optional[str] = Field(None, description="Category of the change")
        assignment_group: Optional[str] = Field(None, description="Group assigned to the change")
        start_date: Optional[str] = Field(None, description="Planned start date (YYYY-MM-DD HH:MM:SS)")
        end_date: Optional[str] = Field(None, description="Planned end date (YYYY-MM-DD HH:MM:SS)")
        work_notes: Optional[str] = Field(None, description="Work notes to add to the change request")
  • Registers the update_change_request tool in the tool_definitions dictionary used by the MCP server, associating the handler function, input schema, return type, description, and serialization method.
    "update_change_request": (
        update_change_request_tool,
        UpdateChangeRequestParams,
        str,
        "Update an existing change request in ServiceNow",
        "str",
    ),
  • Imports the update_change_request function into the tools package namespace, exposing it for use.
    from servicenow_mcp.tools.change_tools import (
        add_change_task,
        approve_change,
        create_change_request,
        get_change_request_details,
        list_change_requests,
        reject_change,
        submit_change_for_approval,
        update_change_request,
    )
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is an update operation, implying mutation, but provides no information about permissions required, whether changes are reversible, what happens to unspecified fields, or any rate limits/constraints. 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 that gets straight to the point with zero wasted words. It's appropriately sized for what it does convey, though it's under-specified rather than concise.

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 11 parameters, 0% schema description coverage, no annotations, and no output schema, this description is severely incomplete. It doesn't explain what fields can be updated, what the change_id parameter represents, what happens after updating, or any behavioral constraints.

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?

Schema description coverage is 0%, meaning none of the 11 parameters have descriptions in the schema. The tool description provides absolutely no information about parameters beyond what's in the name ('update_change_request'), failing to compensate for the complete lack of schema documentation.

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 resource ('an existing change request in ServiceNow'), making the purpose immediately understandable. However, it doesn't differentiate this tool from other update tools in the sibling list (like update_article, update_incident, etc.), which prevents 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. There's no mention of prerequisites (like needing an existing change request ID), when not to use it, or how it differs from related tools like 'create_change_request' or 'update_changeset' in the sibling list.

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