Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

update_epic

Modify an existing ServiceNow epic by updating its description, priority, state, assignment group, assigned user, or adding work notes to track progress and changes.

Instructions

Update an existing epic in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assigned_toNoUser assigned to the epic
assignment_groupNoGroup assigned to the epic
descriptionNoDetailed description of the epic
epic_idYesEpic ID or sys_id
priorityNoPriority of epic (1 is Critical, 2 is High, 3 is Moderate, 4 is Low, 5 is Planning)
short_descriptionNoShort description of the epic
stateNoState of story (-6 is Draft,1 is Ready,2 is Work in progress, 3 is Complete, 4 is Cancelled)
work_notesNoWork notes to add to the epic. Used for adding notes and comments to an epic

Implementation Reference

  • The main handler function that implements the logic for the 'update_epic' tool. It validates parameters using UpdateEpicParams, prepares update data, and sends a PUT request to the ServiceNow rm_epic table API endpoint.
    def update_epic(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        Update an existing epic in ServiceNow.
    
        Args:
            auth_manager: The authentication manager.
            server_config: The server configuration.
            params: The parameters for updating the epic.
    
        Returns:
            The updated epic.
        """
        # Unwrap and validate parameters
        result = _unwrap_and_validate_params(
            params, 
            UpdateEpicParams,
            required_fields=["epic_id"]
        )
        
        if not result["success"]:
            return result
        
        validated_params = result["params"]
        
        # Prepare the request data
        data = {}
        
        # Add optional 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.priority:
            data["priority"] = validated_params.priority
        if validated_params.assignment_group:
            data["assignment_group"] = validated_params.assignment_group
        if validated_params.assigned_to:
            data["assigned_to"] = validated_params.assigned_to
        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/rm_epic/{validated_params.epic_id}"
        
        try:
            response = requests.put(url, json=data, headers=headers)
            response.raise_for_status()
            
            result = response.json()
            
            return {
                "success": True,
                "message": "Epic updated successfully",
                "epic": result["result"],
            }
        except requests.exceptions.RequestException as e:
            logger.error(f"Error updating epic: {e}")
            return {
                "success": False,
                "message": f"Error updating epic: {str(e)}",
            }
  • Pydantic BaseModel defining the input schema/parameters for the update_epic tool, including required epic_id and optional fields for updating epic properties.
    class UpdateEpicParams(BaseModel):
        """Parameters for updating an epic."""
    
        epic_id: str = Field(..., description="Epic ID or sys_id")
        short_description: Optional[str] = Field(None, description="Short description of the epic")
        description: Optional[str] = Field(None, description="Detailed description of the epic")
        priority: Optional[str] = Field(None, description="Priority of epic (1 is Critical, 2 is High, 3 is Moderate, 4 is Low, 5 is Planning)")
        state: Optional[str] = Field(None, description="State of story (-6 is Draft,1 is Ready,2 is Work in progress, 3 is Complete, 4 is Cancelled)")
        assignment_group: Optional[str] = Field(None, description="Group assigned to the epic")
        assigned_to: Optional[str] = Field(None, description="User assigned to the epic")
        work_notes: Optional[str] = Field(None, description="Work notes to add to the epic. Used for adding notes and comments to an epic")
  • Registration of the 'update_epic' tool in the central tool_definitions dictionary within get_tool_definitions function, mapping name to (handler function alias, params schema, return type, description, serialization).
    "update_epic": (
        update_epic_tool,
        UpdateEpicParams,
        str,
        "Update an existing epic in ServiceNow",
        "str",
    ),
  • Import and re-export of the update_epic handler function from epic_tools.py in the tools package __init__.
    from servicenow_mcp.tools.epic_tools import (
        create_epic,
        update_epic,
        list_epics,
    )
  • Import of update_epic function aliased as update_epic_tool and UpdateEpicParams schema for use in tool registration.
        create_epic as create_epic_tool,
        update_epic as update_epic_tool,
        list_epics as list_epics_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. 'Update an existing epic' implies a mutation operation but doesn't disclose behavioral traits like required permissions, whether changes are reversible, rate limits, or what happens to unspecified fields. For a mutation tool with zero annotation coverage, this is a significant gap.

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 action and target.

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 8 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what happens during an update, what the response looks like, or any system constraints. The high schema coverage helps with parameters, but behavioral and output context is missing.

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%, so the schema already documents all 8 parameters thoroughly with descriptions and defaults. The description adds no additional parameter information beyond what's in the schema, meeting the baseline for high 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 verb ('Update') and resource ('an existing epic in ServiceNow'), making the purpose unambiguous. However, it doesn't differentiate this tool from other update tools like update_story or update_change_request, which would require mentioning specific epic fields or context.

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. With sibling tools like update_story and update_change_request, there's no indication of when an epic update is appropriate versus other entity updates, nor any prerequisites or constraints mentioned.

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

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