Skip to main content
Glama
sonisoft-cnanda

now-sdk-ext-mcp

Execute Action

execute_action
Destructive

Execute a ServiceNow Flow Designer action by scoped name, passing inputs and selecting foreground or background mode. This triggers predefined automation without manual UI steps.

Instructions

Execute a ServiceNow Flow Designer action by scoped name. Actions are the lowest-level building blocks in Flow Designer (e.g., lookup record, create task, send notification).

In foreground mode (default), the call blocks until the action completes and returns outputs directly. Actions typically complete quickly and foreground mode is usually appropriate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
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.
inputsNoInput name-value pairs to pass to the flow/subflow/action. Keys are the input variable names defined in Flow Designer.
timeoutNoTimeout in milliseconds for the execution. Only applies to foreground mode. Default is the ServiceNow server default (~30s).
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").
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds useful behavioral context: foreground blocks, background returns immediately with a context ID, and quick skips execution details. It does not restate annotations and provides mode-specific behavior beyond what annotations offer.

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 concise, with a clear one-sentence purpose followed by a focused paragraph on mode behavior. Every sentence adds value and no content is wasted.

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

Completeness4/5

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

The description covers the main execution modes, how to retrieve background results (naming follow-up tools), and when to use quick mode. It does not explain error handling or return formats, but the lack of an output schema shifts some burden to the description. Overall, it is sufficiently complete for a tool with 7 parameters and no output schema.

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 already provides full descriptions for all 7 parameters (100% coverage). The tool description does not add significant per-parameter detail, but it does contextualize the mode parameter within the foreground/background discussion. Baseline 3 is appropriate.

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?

States a specific verb ('Execute') plus a specific resource type ('ServiceNow Flow Designer action by scoped name'). The phrase 'Actions are the lowest-level building blocks' clearly distinguishes it from sibling tools like execute_flow and execute_subflow.

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

Usage Guidelines4/5

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

Provides clear guidance on when to use foreground vs background modes and suggests background for flows with approval/wait steps. However, it does not explicitly name alternative tools for running full flows or subflows, so guidance on tool selection is implicit rather than explicit.

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