Skip to main content
Glama
SmartSuiteFoundry

SmartSuite MCP Server

smartsuite_create_field

Create any field type in a SmartSuite application, including rollup, lookup, and AI-populated fields. Supply field type and label; optional params override defaults.

Instructions

Create a field of any type in an application (including rollup and lookup fields — not just formulas). Requires readwrite/admin mode AND SMARTSUITE_ENABLE_SCHEMA_WRITE=true. You supply fieldType + label and an OPTIONAL sparse params object; SmartSuite fills type defaults, so most fields need no params. Provide params only where they matter, e.g.: singleselectfield/multipleselectfield/statusfield → {choices:[{label, value_help_text?, weight?}]} where value_help_text is the option DESCRIPTION shown in the dropdown and weight is its NUMERIC value (used by formulas/rollups); e.g. {choices:[{label:"High", value_help_text:"Ship this week", weight:3}]}. Choice colors and order are auto-assigned if omitted so the dropdown renders correctly (status choices take no weight/description); linkedrecordfield → {linked_application:"", entries_allowed:"single"|"multiple"} (backlink auto-created); rollupfield → {linked_field:"", field_selection:"", function:"sum"|"count"|"min"|"max"|"average"|"concatenate"|...}; lookupfield → {linked_field, field_selection}; numberfield → {precision, separator}; currencyfield → {currency:"USD"}; textfield → {max_length}. (For formula fields use smartsuite_create_formula_field.) AI FIELDS: to make a field AI-populated, pass aiPrompt — a plain-text prompt where {{field_slug}} inserts a live reference to another field (e.g. "Summarize {{title}} for {{s096c9e74e}}"). The tool builds the correct rich-text instructions with field-reference pills and enables the AI agent; put the AI model/credential and other ai_agent settings in params.ai_agent if needed. (This is the reliable way to set dynamic AI prompts — do NOT hand-build ai_agent.instructions.) The slug is generated and the field is placed in the record-view layout. Dry-run preview unless confirm:true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelYesField display label.
paramsNoOptional sparse field params; omit to accept type defaults. See the tool description for which params each type needs.
confirmNoMust be true to create (default false = preview).
aiPromptNoOptional: make this an AI-populated field. Plain-text prompt where {{field_slug}} inserts a live reference to another field. The tool builds the rich-text AI instructions (with field pills) and enables the AI agent.
fieldTypeYesSmartSuite field type, e.g. textfield, textareafield, richtextareafield, numberfield, currencyfield, percentfield, datefield, duedatefield, singleselectfield, multipleselectfield, statusfield, yesnofield, linkedrecordfield, userfield, emailfield, phonefield, linkfield, filefield, addressfield, ratingfield, durationfield, timefield, checklistfield, tagsfield, colorpickerfield.
applicationIdYesThe application (table) ID.
afterFieldSlugNoOptional: place the new field after this field slug (default: end).
Behavior4/5

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

Annotations already indicate readOnlyHint=false, so description confirms it's a write operation. Adds significant behavioral context: dry-run preview, auto-filling type defaults, auto-creation of backlinks, AI prompt handling. These go beyond the annotation.

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?

Description is lengthy but well-structured, front-loading the core purpose. Uses bullet-like examples and conditional sections. Every sentence conveys necessary information without redundancy.

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 the tool's complexity (7 params, nested objects, many field types), the description is remarkably thorough. Covers prerequisites, default behaviors, field-type-specific parameters, AI fields, and layout placement. No output schema, but description compensates with operation details.

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% but the description provides extensive, type-specific guidance for the params field (e.g., choices format for select fields, linkedrecordfield requirements, rollup/lookup syntax). Also explains the aiPrompt parameter in depth.

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 opens with 'Create a field of any type in an application' and lists many field types including rollup/lookup. It distinguishes from sibling tool smartsuite_create_formula_field by explicitly noting formula fields are handled elsewhere.

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?

Clearly states prerequisites (readwrite/admin mode and SMARTSUITE_ENABLE_SCHEMA_WRITE=true). Provides guidance on when to provide params ('only where they matter') and when to use the sibling tool for formulas. Also mentions dry-run preview unless confirm:true.

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/SmartSuiteFoundry/smartsuite-mcp-server'

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