Skip to main content
Glama
sonisoft-cnanda

now-sdk-ext-mcp

Create Workflow

create_workflow

Create a complete ServiceNow workflow from a single specification, including activities, transitions, and optional publishing.

Instructions

Create a complete ServiceNow workflow from a single specification. Orchestrates: create workflow record -> create version -> create activities -> create transitions -> optionally publish.

Activities are referenced in transitions by their id field (if set) or their array index (as a string like '0', '1', etc.).

IMPORTANT: This creates multiple records on the ServiceNow instance (workflow, version, activities, transitions). Review the specification carefully.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instanceNoThe ServiceNow instance auth alias (e.g., "myinstance", "prod"). If not provided, falls back to the SN_AUTH_ALIAS environment variable.
nameYesName of the workflow.
tableYesTarget table for the workflow (e.g., "incident", "change_request").
descriptionNoDescription of the workflow.
activitiesYesList of workflow activities to create.
transitionsNoTransitions between activities.
publishNoWhether to publish the workflow after creation. Requires start_activity to be specified.
start_activityNoActivity id or index to use as the start activity. Required when publish is true.
conditionNoWorkflow trigger condition.
accessNoWorkflow access level.
templateNoWhether the workflow is a template.
activeNoWhether the workflow version is active.
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the multi-record creation, the orchestration order, and the transition referencing convention. However, it omits details on return values, error handling, transactional behavior, and what happens on failure.

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 highly concise: one sentence states purpose, followed by a brief list of steps, a key referencing detail, and a warning. Every sentence adds value, and the important information is front-loaded.

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?

Given the complexity and lack of output schema, the description explains the orchestration and referencing method but does not specify the return value (e.g., workflow sys_id) or behavior in failure scenarios. It partially compensates for the missing output schema but could be more complete.

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?

Input schema covers 100% of parameters with individual descriptions. The description adds value by explaining how activities are referenced in transitions. No additional parameter-level semantics beyond schema.

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 tool creates a complete ServiceNow workflow from a single specification, listing the orchestration steps. This distinguishes it from sibling tools which are mostly CRUD or execution operations, none of which create workflows.

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?

The description warns that it creates multiple records and advises careful review, setting a clear context for a complex creation operation. However, it does not explicitly state when to use versus alternatives or when not to use this tool.

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