Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

list_workflow_versions

Retrieve and display available versions of a specific ServiceNow workflow, allowing users to manage workflow evolution and track changes over time.

Instructions

List workflow versions from ServiceNow

Input Schema

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

Implementation Reference

  • The core handler function for the 'list_workflow_versions' tool. It validates parameters using ListWorkflowVersionsParams, constructs a ServiceNow API query for the wf_workflow_version table filtered by workflow_id, fetches the data via REST GET, 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 BaseModel defining the input schema for the tool: requires workflow_id, optional limit and offset.
    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")
  • Registers the tool in the central get_tool_definitions() dictionary used by the MCP server, mapping name to (handler, param_model, return_type, description, serialization).
    "list_workflow_versions": (
        list_workflow_versions_tool,
        ListWorkflowVersionsParams,
        str,  # Expects JSON string
        "List workflow versions from ServiceNow",
        "json",  # Tool returns list/dict
    ),
  • Imports the list_workflow_versions function into the tools package 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,
    )
  • Helper function used by the handler to unwrap and validate parameters using the schema model.
    def _unwrap_params(params: Any, param_class: Type[T]) -> Dict[str, Any]:
        """
        Unwrap parameters if they're wrapped in a Pydantic model.
        This helps handle cases where the parameters are passed as a model instead of a dict.
        """
        if isinstance(params, dict):
            return params
        if isinstance(params, param_class):
            return params.dict(exclude_none=True)
        return params
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 offers minimal information. It doesn't mention whether this is a read-only operation, what permissions might be required, how results are structured, whether pagination is handled, or any rate limits. The description merely restates the tool name without adding meaningful behavioral context.

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 extremely concise at just 5 words, with zero wasted language. It's front-loaded with the essential action and resource, making it efficient for quick scanning. Every word earns its place in this minimal description.

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 tool with 3 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what workflow versions are, how they differ from workflows, what information is returned, or any behavioral characteristics. The description fails to compensate for the lack of structured metadata that would help an agent understand this tool's proper 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?

With 100% schema description coverage, the schema already documents all three parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema. The baseline score of 3 reflects adequate parameter documentation through the schema alone, though the description contributes nothing extra.

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 ('workflow versions from ServiceNow'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'list_workflows' or 'get_workflow_details', which would require more specificity about what distinguishes workflow versions from workflows themselves.

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', 'get_workflow_details', and 'get_workflow_activities'), there's no indication of when this specific version-listing tool is appropriate versus other workflow-related tools.

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