Skip to main content
Glama
sonisoft-cnanda

now-sdk-ext-mcp

Execute Flow

execute_flow

Triggers a published ServiceNow flow by its scoped name. Supports foreground mode for synchronous results and background mode for flows with approvals or wait steps.

Instructions

Execute a published ServiceNow Flow Designer flow by scoped name. Runs the flow using sn_fd.FlowAPI via a background script.

In foreground mode (default), the call blocks until the flow completes and returns outputs directly. In background mode, it returns immediately with a context ID that you can poll with get_flow_context_status.

IMPORTANT: Flows with approval or wait steps MUST use background mode — foreground mode will fail if the flow enters a waiting state.

NOTE: This tool requires the flow to be published. If you are iterating and building a flow that may not be published yet, use test_flow instead — it tests the flow in its current draft state, exactly as the 'Test' button in Flow Designer does.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instanceNoThe ServiceNow instance auth alias to use. This is the alias configured via `now-sdk auth --add` (e.g., "myinstance", "prod", "test"). The user will typically refer to this by name when saying things like "on my myinstance instance". If not provided, falls back to the SN_AUTH_ALIAS environment variable.
scoped_nameYesScoped name of the flow/subflow/action to execute (e.g., "global.my_flow", "x_myapp_custom.create_incident_subflow").
inputsNoInput name-value pairs to pass to the flow/subflow/action. Keys are the input variable names defined in Flow Designer.
modeNoExecution mode. "foreground" (default) runs synchronously and returns outputs when complete. "background" returns immediately with a context ID — use get_flow_context_status to poll, then get_flow_outputs or get_flow_error to retrieve results. Use background for flows with approval/wait steps.
timeoutNoTimeout in milliseconds for the execution. Only applies to foreground mode. Default is the ServiceNow server default (~30s).
quickNoSkip creation of execution detail records for better performance. Default false. Use true in CI/CD or when you don't need step-level detail.
scopeNoScope context for script execution. Can be a scope name (e.g., "x_myapp_custom") or sys_id. Use when the flow is in a scoped app.
Behavior4/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. It explains foreground blocks, background returns a context ID, and mentions the 'quick' parameter skips detail records. However, it does not disclose permissions, error behavior, or side effects beyond the basic execution flow.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with sections (IMPORTANT, NOTE) and front-loaded with the core purpose. It is slightly verbose but every sentence adds value, so conciseness is good.

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

Completeness5/5

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

Given 7 parameters, no output schema, and complexity of execution modes, the description covers return behavior (foreground vs background), references sister tools (get_flow_context_status, test_flow), and addresses edge cases (approval steps, unpublished flows). It is comprehensive for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds value by explaining the purpose of each parameter (e.g., 'quick' for performance, 'mode' for synchronous vs async, 'scope' for scoped app context). This goes beyond the raw schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Execute' and the resource 'published ServiceNow Flow Designer flow by scoped name'. It distinguishes from sibling 'test_flow' by noting the requirement for the flow to be published.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance on foreground vs background modes, including when to use background (flows with approval/wait steps) and when to use 'test_flow' instead (unpublished flows). This helps the agent select the correct tool and execution mode.

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/sonisoft-cnanda/now-sdk-ext-mcp'

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