Skip to main content
Glama
JLKmach

ServiceNow MCP Server

by JLKmach

list_script_includes

Retrieve and filter script includes from ServiceNow instances to manage server-side logic and client-callable functions with pagination support.

Instructions

List script includes from ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of script includes to return
offsetNoOffset for pagination
activeNoFilter by active status
client_callableNoFilter by client callable status
queryNoSearch query for script includes

Implementation Reference

  • The handler function that implements the core logic for the 'list_script_includes' tool. It queries the ServiceNow sys_script_include table via REST API, applies filters, and returns formatted results.
    def list_script_includes(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: ListScriptIncludesParams,
    ) -> Dict[str, Any]:
        """List script includes from ServiceNow.
        
        Args:
            config: The server configuration.
            auth_manager: The authentication manager.
            params: The parameters for the request.
            
        Returns:
            A dictionary containing the list of script includes.
        """
        try:
            # Build the URL
            url = f"{config.instance_url}/api/now/table/sys_script_include"
            
            # Build query parameters
            query_params = {
                "sysparm_limit": params.limit,
                "sysparm_offset": params.offset,
                "sysparm_display_value": "true",
                "sysparm_exclude_reference_link": "true",
                "sysparm_fields": "sys_id,name,script,description,api_name,client_callable,active,access,sys_created_on,sys_updated_on,sys_created_by,sys_updated_by"
            }
            
            # Add filters if provided
            query_parts = []
            
            if params.active is not None:
                query_parts.append(f"active={str(params.active).lower()}")
                
            if params.client_callable is not None:
                query_parts.append(f"client_callable={str(params.client_callable).lower()}")
                
            if params.query:
                query_parts.append(f"nameLIKE{params.query}")
                
            if query_parts:
                query_params["sysparm_query"] = "^".join(query_parts)
                
            # Make the request
            headers = auth_manager.get_headers()
            
            response = requests.get(
                url,
                params=query_params,
                headers=headers,
                timeout=30,
            )
            response.raise_for_status()
            
            # Parse the response
            data = response.json()
            script_includes = []
            
            for item in data.get("result", []):
                script_include = {
                    "sys_id": item.get("sys_id"),
                    "name": item.get("name"),
                    "description": item.get("description"),
                    "api_name": item.get("api_name"),
                    "client_callable": item.get("client_callable") == "true",
                    "active": item.get("active") == "true",
                    "access": item.get("access"),
                    "created_on": item.get("sys_created_on"),
                    "updated_on": item.get("sys_updated_on"),
                    "created_by": item.get("sys_created_by", {}).get("display_value"),
                    "updated_by": item.get("sys_updated_by", {}).get("display_value"),
                }
                script_includes.append(script_include)
                
            return {
                "success": True,
                "message": f"Found {len(script_includes)} script includes",
                "script_includes": script_includes,
                "total": len(script_includes),
                "limit": params.limit,
                "offset": params.offset,
            }
            
        except Exception as e:
            logger.error(f"Error listing script includes: {e}")
            return {
                "success": False,
                "message": f"Error listing script includes: {str(e)}",
                "script_includes": [],
                "total": 0,
                "limit": params.limit,
                "offset": params.offset,
            }
  • Pydantic model defining the input parameters (limit, offset, filters) for the list_script_includes tool.
    class ListScriptIncludesParams(BaseModel):
        """Parameters for listing script includes."""
        
        limit: int = Field(10, description="Maximum number of script includes to return")
        offset: int = Field(0, description="Offset for pagination")
        active: Optional[bool] = Field(None, description="Filter by active status")
        client_callable: Optional[bool] = Field(None, description="Filter by client callable status")
        query: Optional[str] = Field(None, description="Search query for script includes")
  • Registers the 'list_script_includes' tool in the central tool_definitions dictionary used by the MCP server to expose tools, linking the handler, schema, description, and serialization method.
    "list_script_includes": (
        list_script_includes_tool,
        ListScriptIncludesParams,
        Dict[str, Any],  # Expects dict
        "List script includes from ServiceNow",
        "raw_dict",  # Tool returns raw dict
    ),
  • Imports the list_script_includes function into the tools package namespace, making it available for further registration.
    from servicenow_mcp.tools.script_include_tools import (
        create_script_include,
        delete_script_include,
        get_script_include,
        list_script_includes,
        update_script_include,
    )
  • Includes 'list_script_includes' in the __all__ list, explicitly exporting it from the tools module.
    "list_script_includes",
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without disclosing behavioral traits. It doesn't mention whether this is a read-only operation, potential rate limits, authentication needs, pagination behavior, or what the return format looks like, leaving significant gaps for a tool with 5 parameters.

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 waste—'List script includes from ServiceNow'—front-loading the core purpose without unnecessary elaboration. Every word earns its place, making it appropriately sized for its function.

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 of 5 parameters, no annotations, and no output schema, the description is incomplete. It fails to explain return values, behavioral constraints, or usage context, leaving the agent with insufficient information to effectively invoke this tool beyond basic parameter input.

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 fully documents all 5 parameters. The description adds no parameter-specific information beyond what's in the schema, maintaining the baseline score of 3 where the schema does the heavy lifting without additional value from 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 ('List') and resource ('script includes from ServiceNow'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'get_script_include' or 'create_script_include' beyond the basic list vs. get/create distinction, missing explicit scope comparison.

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 like 'get_script_include' for single records or 'create_script_include' for creation. The description lacks context about filtering capabilities or prerequisites, offering only a basic statement without usage context.

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

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