Skip to main content
Glama
JLKmach

ServiceNow MCP Server

by JLKmach

list_workflow_versions

Retrieve and manage workflow version history from ServiceNow to track changes, compare iterations, and maintain process documentation.

Instructions

List workflow versions from ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_idYesWorkflow ID or sys_id
limitNoMaximum number of records to return
offsetNoOffset to start from

Implementation Reference

  • The main handler function that executes the tool logic: unwraps parameters using ListWorkflowVersionsParams schema, authenticates, queries the ServiceNow wf_workflow_version table API with workflow_id filter, and returns versions list with metadata.
    def list_workflow_versions(
        auth_manager: AuthManager,
        server_config: ServerConfig,
        params: Dict[str, Any],
    ) -> Dict[str, Any]:
        """
        List versions of a specific workflow.
        
        Args:
            auth_manager: Authentication manager
            server_config: Server configuration
            params: Parameters for listing workflow versions
            
        Returns:
            Dict[str, Any]: List of workflow versions
        """
        # Unwrap parameters if needed
        params = _unwrap_params(params, ListWorkflowVersionsParams)
        
        # Get the correct auth_manager and server_config
        try:
            auth_manager, server_config = _get_auth_and_config(auth_manager, server_config)
        except ValueError as e:
            logger.error(f"Error getting auth and config: {e}")
            return {"error": str(e)}
        
        workflow_id = params.get("workflow_id")
        if not workflow_id:
            return {"error": "Workflow ID is required"}
        
        # Convert parameters to ServiceNow query format
        query_params = {
            "sysparm_query": f"workflow={workflow_id}",
            "sysparm_limit": params.get("limit", 10),
            "sysparm_offset": params.get("offset", 0),
        }
        
        # Make the API request
        try:
            headers = auth_manager.get_headers()
            url = f"{server_config.instance_url}/api/now/table/wf_workflow_version"
            
            response = requests.get(url, headers=headers, params=query_params)
            response.raise_for_status()
            
            result = response.json()
            return {
                "versions": result.get("result", []),
                "count": len(result.get("result", [])),
                "total": int(response.headers.get("X-Total-Count", 0)),
                "workflow_id": workflow_id,
            }
        except requests.RequestException as e:
            logger.error(f"Error listing workflow versions: {e}")
            return {"error": str(e)}
        except Exception as e:
            logger.error(f"Unexpected error listing workflow versions: {e}")
            return {"error": str(e)}
  • Pydantic model defining the input parameters for the tool: required workflow_id, optional limit and offset for pagination.
    class ListWorkflowVersionsParams(BaseModel):
        """Parameters for listing workflow versions."""
        
        workflow_id: str = Field(..., description="Workflow ID or sys_id")
        limit: Optional[int] = Field(10, description="Maximum number of records to return")
        offset: Optional[int] = Field(0, description="Offset to start from")
  • Tool registration in get_tool_definitions(): maps name to (aliased handler, input schema, return type hint, description, serialization method) used by MCP server.
    "list_workflow_versions": (
        list_workflow_versions_tool,
        ListWorkflowVersionsParams,
        str,  # Expects JSON string
        "List workflow versions from ServiceNow",
        "json",  # Tool returns list/dict
    ),
  • Imports list_workflow_versions from workflow_tools.py into tools namespace for exposure.
    from servicenow_mcp.tools.workflow_tools import (
        activate_workflow,
        add_workflow_activity,
        create_workflow,
        deactivate_workflow,
        delete_workflow_activity,
        get_workflow_activities,
        get_workflow_details,
        list_workflow_versions,
        list_workflows,
        reorder_workflow_activities,
        update_workflow,
        update_workflow_activity,
    )
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 but provides minimal information. It doesn't mention whether this is a read-only operation, what permissions are required, whether results are paginated beyond the limit/offset parameters, or what format the returned versions will have. For a listing 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 states exactly what the tool does without any wasted words. It's appropriately sized for a straightforward listing operation and gets directly to the point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a listing tool with good schema coverage but no annotations and no output schema, the description is minimally adequate. It states what the tool does but doesn't provide important contextual information about behavioral characteristics, usage scenarios, or result format that would be helpful for an agent.

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 input schema has 100% description coverage, so all parameters are documented in the schema itself. The description adds no additional parameter information beyond what's already in the schema descriptions. This meets the baseline expectation when schema coverage is complete.

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 ('List') and resource ('workflow versions from ServiceNow'), making the purpose immediately understandable. However, it doesn't distinguish this tool from potential sibling list tools (like list_workflows or list_workflow_activities), which would require more specific differentiation to earn a 5.

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 many sibling tools available (including list_workflows and get_workflow_details), there's no indication of when this specific listing operation is appropriate versus other listing or retrieval operations in the same domain.

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