Skip to main content
Glama
vparlapalli490

ServiceNow MCP Server

list_workflow_versions

Retrieve and display available versions of a specific workflow from ServiceNow to track changes and manage process evolution.

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 implementing the list_workflow_versions tool. It validates input, constructs a ServiceNow API query for wf_workflow_version table filtered by workflow_id, fetches the data, 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 schema for the tool, including required workflow_id and optional pagination parameters.
    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")
  • MCP tool registration entry in get_tool_definitions() dictionary, linking the handler function, input schema, description, and serialization details.
    "list_workflow_versions": (
        list_workflow_versions_tool,
        ListWorkflowVersionsParams,
        str,  # Expects JSON string
        "List workflow versions from ServiceNow",
        "json",  # Tool returns list/dict
    ),
  • Import statement in tools/__init__.py that exposes list_workflow_versions function for use across the package.
    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 but offers minimal behavioral context. It doesn't mention that this is a read-only operation (implied by 'list'), doesn't discuss pagination behavior (though parameters suggest it), doesn't describe response format, and doesn't mention authentication or rate limits. The description adds almost no value beyond what's obvious from the tool name.

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. It's appropriately sized for a simple list operation and front-loads the essential information. Every word earns its place.

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 simple list tool with good schema coverage but no annotations or output schema, the description is minimally adequate. It states what the tool does but lacks behavioral context, usage guidance, and output information. The agent can infer basic usage but would need to rely heavily on the schema and trial-and-error for proper invocation.

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 three parameters. The description adds no parameter information beyond what's already in the schema - it doesn't clarify what a 'workflow version' entails or provide context about the ID format. Baseline 3 is appropriate when the schema does all the work.

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'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list_workflows' or 'get_workflow_details' - the agent must infer this lists versions of a specific workflow rather than 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?

No guidance is provided about when to use this tool versus alternatives. The agent must deduce from the name and parameters that this is for listing versions of a specific workflow, but there's no explicit comparison to 'list_workflows' (which lists workflows themselves) or 'get_workflow_details' (which might get details of a specific workflow version).

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