Skip to main content
Glama
vparlapalli490

ServiceNow MCP Server

delete_script_include

Remove a script include from a ServiceNow instance by specifying its ID or name. This action deletes server-side scripts used for custom business logic or automation.

Instructions

Delete a script include in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
script_include_idYesScript include ID or name

Implementation Reference

  • The handler function that implements the delete_script_include tool logic. It retrieves the script include by ID, constructs the API URL, sends a DELETE request to ServiceNow, and returns a response indicating success or failure.
    def delete_script_include(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: DeleteScriptIncludeParams,
    ) -> ScriptIncludeResponse:
        """Delete a script include from 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 delete
        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"]
        name = script_include["name"]
        
        # Build the URL
        url = f"{config.instance_url}/api/now/table/sys_script_include/{sys_id}"
        
        # Make the request
        headers = auth_manager.get_headers()
        
        try:
            response = requests.delete(
                url,
                headers=headers,
                timeout=30,
            )
            response.raise_for_status()
            
            return ScriptIncludeResponse(
                success=True,
                message=f"Deleted script include: {name}",
                script_include_id=sys_id,
                script_include_name=name,
            )
            
        except Exception as e:
            logger.error(f"Error deleting script include: {e}")
            return ScriptIncludeResponse(
                success=False,
                message=f"Error deleting script include: {str(e)}",
            ) 
  • Pydantic BaseModel defining the input schema for the delete_script_include tool, requiring a script_include_id.
    class DeleteScriptIncludeParams(BaseModel):
        """Parameters for deleting a script include."""
        
        script_include_id: str = Field(..., description="Script include ID or name")
  • Tool registration entry in get_tool_definitions() dictionary, mapping the tool name to its handler (aliased), input schema, return type hint, description, and serialization method.
    "delete_script_include": (
        delete_script_include_tool,
        DeleteScriptIncludeParams,
        str,  # Expects JSON string
        "Delete a script include in ServiceNow",
        "json_dict",  # Tool returns Pydantic model
    ),
  • Import statement in tools/__init__.py that re-exports delete_script_include for convenient access from the tools package.
    from servicenow_mcp.tools.script_include_tools import (
        create_script_include,
        delete_script_include,
        get_script_include,
        list_script_includes,
        update_script_include,
    )
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Delete' implies a destructive mutation, the description doesn't specify whether this action is reversible, what permissions are required, or what happens upon success/failure (e.g., error handling). It lacks critical context for a destructive operation.

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's front-loaded with the key action and resource, making it highly efficient and easy to parse.

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 destructive tool with no annotations and no output schema, the description is inadequate. It doesn't explain the consequences of deletion, success indicators, error conditions, or required permissions. Given the complexity of a delete operation in ServiceNow, more context is needed for safe and effective use.

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%, with the parameter 'script_include_id' clearly documented in the schema as 'Script include ID or name'. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline for high schema coverage without adding value.

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 ('Delete') and target resource ('a script include in ServiceNow'), making the purpose immediately understandable. However, it doesn't differentiate this tool from other deletion-related tools in the sibling list (like delete_workflow_activity), 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. It doesn't mention prerequisites (e.g., needing the script_include_id from get_script_include or list_script_includes), nor does it warn about irreversible deletion or permission requirements. The sibling tools include create_script_include and update_script_include, but no comparison is made.

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