Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

update_script_include

Modify an existing ServiceNow script include by updating its code, description, API name, access settings, or activation status to maintain custom business logic.

Instructions

Update an existing script include in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accessNoAccess level of the script include
activeNoWhether the script include is active
api_nameNoAPI name of the script include
client_callableNoWhether the script include is client callable
descriptionNoDescription of the script include
scriptNoScript content
script_include_idYesScript include ID or name

Implementation Reference

  • The main handler function that implements the update_script_include tool. It fetches the existing script include, constructs the update payload from optional parameters, and performs a PATCH request to the ServiceNow API endpoint.
    def update_script_include(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: UpdateScriptIncludeParams,
    ) -> ScriptIncludeResponse:
        """Update an existing script include in ServiceNow.
        
        Args:
            config: The server configuration.
            auth_manager: The authentication manager.
            params: The parameters for the request.
            
        Returns:
            A response indicating the result of the operation.
        """
        # First, get the script include to update
        get_params = GetScriptIncludeParams(script_include_id=params.script_include_id)
        get_result = get_script_include(config, auth_manager, get_params)
        
        if not get_result["success"]:
            return ScriptIncludeResponse(
                success=False,
                message=get_result["message"],
            )
            
        script_include = get_result["script_include"]
        sys_id = script_include["sys_id"]
        
        # Build the URL
        url = f"{config.instance_url}/api/now/table/sys_script_include/{sys_id}"
        
        # Build the request body
        body = {}
        
        if params.script is not None:
            body["script"] = params.script
            
        if params.description is not None:
            body["description"] = params.description
            
        if params.api_name is not None:
            body["api_name"] = params.api_name
            
        if params.client_callable is not None:
            body["client_callable"] = str(params.client_callable).lower()
            
        if params.active is not None:
            body["active"] = str(params.active).lower()
            
        if params.access is not None:
            body["access"] = params.access
            
        # If no fields to update, return success
        if not body:
            return ScriptIncludeResponse(
                success=True,
                message=f"No changes to update for script include: {script_include['name']}",
                script_include_id=sys_id,
                script_include_name=script_include["name"],
            )
            
        # Make the request
        headers = auth_manager.get_headers()
        
        try:
            response = requests.patch(
                url,
                json=body,
                headers=headers,
                timeout=30,
            )
            response.raise_for_status()
            
            # Parse the response
            data = response.json()
            
            if "result" not in data:
                return ScriptIncludeResponse(
                    success=False,
                    message=f"Failed to update script include: {script_include['name']}",
                )
                
            result = data["result"]
            
            return ScriptIncludeResponse(
                success=True,
                message=f"Updated script include: {result.get('name')}",
                script_include_id=result.get("sys_id"),
                script_include_name=result.get("name"),
            )
            
        except Exception as e:
            logger.error(f"Error updating script include: {e}")
            return ScriptIncludeResponse(
                success=False,
                message=f"Error updating script include: {str(e)}",
            )
  • Pydantic model defining the input parameters for the update_script_include tool, including the script include identifier and optional fields to update.
    class UpdateScriptIncludeParams(BaseModel):
        """Parameters for updating a script include."""
        
        script_include_id: str = Field(..., description="Script include ID or name")
        script: Optional[str] = Field(None, description="Script content")
        description: Optional[str] = Field(None, description="Description of the script include")
        api_name: Optional[str] = Field(None, description="API name of the script include")
        client_callable: Optional[bool] = Field(None, description="Whether the script include is client callable")
        active: Optional[bool] = Field(None, description="Whether the script include is active")
        access: Optional[str] = Field(None, description="Access level of the script include")
  • Registration of the update_script_include tool in the central tool_definitions dictionary, mapping the tool name to its handler, params schema, return type, description, and serialization method.
    "update_script_include": (
        update_script_include_tool,
        UpdateScriptIncludeParams,
        ScriptIncludeResponse,  # Expects Pydantic model
        "Update an existing script include in ServiceNow",
        "raw_pydantic",  # Tool returns Pydantic model
    ),
  • Import and aliasing of the update_script_include handler function as update_script_include_tool for use in tool registration.
    from servicenow_mcp.tools.script_include_tools import (
        update_script_include as update_script_include_tool,
    )
  • Pydantic model for the response returned by the update_script_include handler.
    class ScriptIncludeResponse(BaseModel):
        """Response from script include operations."""
        
        success: bool = Field(..., description="Whether the operation was successful")
        message: str = Field(..., description="Message describing the result")
        script_include_id: Optional[str] = Field(None, description="ID of the affected script include")
        script_include_name: Optional[str] = Field(None, description="Name of the affected script include")
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 mention required permissions, whether changes are reversible, potential side effects, error conditions, or what the response looks like. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a tool with good schema documentation and is perfectly front-loaded.

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 7 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what happens when parameters are omitted, whether partial updates are allowed, what the tool returns, or any behavioral constraints. The combination of mutation operation, multiple parameters, and lack of structured metadata requires more descriptive context.

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 all parameters are documented in the schema. The description adds no additional parameter information beyond what's already in the structured schema. According to the scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 resource ('an existing script include in ServiceNow'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'update_article' or 'update_change_request' beyond the resource type, and doesn't specify what aspects can be updated.

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. It doesn't mention prerequisites (like needing the script_include_id), when not to use it, or how it differs from related tools like 'create_script_include' or 'delete_script_include' that appear 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

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