Skip to main content
Glama
SmartSuiteFoundry

SmartSuite MCP Server

by SmartSuiteFoundry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

smartsuite_create_automation

Create an automation in a SmartSuite solution by providing a trigger and actions.

Instructions

Create an automation in a solution. Requires readwrite/admin mode AND SMARTSUITE_ENABLE_SCHEMA_WRITE=true. You supply the trigger (an object with trigger_reference.trigger_id and inputs) and the actions; use smartsuite_describe_automation_step on a similar existing automation to learn the exact trigger/action/input shapes and option values — note that a BRAND-NEW solution has no such automation to copy, so build the first one in the UI and read it back, or expect to discover required keys one 400 at a time (the errors are precise, e.g. "trigger.trigger_reference.trigger_id is required"). Pass actions either as the native nested actionGroups ([{actions:{actions:[...]}}]) or as a flat actions array (wrapped into one group automatically). Pass credentialId once to fill it onto the trigger and every action that omits one. automaticDescription (the UI display phrase) and timezone are optional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelYesAutomation name.
actionsNoFlat list of action objects; wrapped into a single action group. Each: { action_reference:{integration_id, action_id, instance_id}, credential_id?, inputs:[...], record_list?:{...} }.
triggerYesTrigger object: { trigger_reference:{integration_id, trigger_id}, credential_id?, inputs:[...], conditions?:{...} }.
timezoneNoOptional IANA timezone (e.g. America/Chicago).
solutionIdYesThe solution ID the automation belongs to.
actionGroupsNoNative action groups: [{actions:{actions:[<action>...]}}]. Mutually exclusive with `actions`.
credentialIdNoOptional: fill this credential_id onto the trigger and any action missing one.
automaticDescriptionNoOptional UI display phrase (phrase-builder JSON string). Omit to leave blank.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.8

TDQS

A4.6/5.0
Behavior5/5

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

Annotations carry only readOnlyHint=false, so the description bears the load and delivers: required auth/feature-flag mode, the greenfield-solution caveat with its 400-at-a-time discovery loop, example error text, and the automatic wrapping of a flat actions array into one group. This is exactly the behavioral context structured fields do not provide.

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?

Purpose is front-loaded in the first sentence, and the dense follow-on clauses each carry actionable detail rather than filler. The single long paragraph is information-rich but could be broken up for scanability.

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?

For a complex write tool with 8 params, nested trigger/action objects and no output schema, the description covers construction strategy, credential handling, both action shapes, the auth gate, and failure behavior. There is no output schema to excuse, and nothing an agent needs in order to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: that flat `actions` is auto-wrapped while `actionGroups` is the native form, and that a single `credentialId` fans out onto the trigger and any action lacking one. Most other field semantics (timezone, automaticDescription, solutionId) are already in the schema, so it does not go far beyond the baseline.

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 and resource ('Create an automation in a solution'), which unambiguously distinguishes it from smartsuite_update_automation, smartsuite_describe_automation and smartsuite_list_automations. No schema opening required to know what it does.

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?

Gives concrete preconditions (readwrite/admin mode AND SMARTSUITE_ENABLE_SCHEMA_WRITE=true) and points the agent at smartsuite_describe_automation_step to learn trigger/action shapes. It does not explicitly contrast create-vs-update, but the create scope plus the sibling pointer gives clear operational context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools