Skip to main content
Glama
SmartSuiteFoundry

SmartSuite MCP Server

smartsuite_update_dashboard

Update a dashboard by renaming it, changing its description, and editing tabs, footer, or style. Tabs can be added, renamed, reordered, or removed.

Instructions

Update a dashboard: rename (label), change description, and/or edit tabs, footer, and style. Requires readwrite/admin mode AND SMARTSUITE_ENABLE_SCHEMA_WRITE=true. tabs REPLACES the tab set — pass the full desired list as {id?, name, order?}; include a tab's existing id to rename/reorder it (get ids from smartsuite_describe_dashboard), omit id to add a new tab, drop a tab to remove it (its widgets go too). tabsEnabled toggles the tab bar; tabsPosition is "left"/"top". footer/style are merged onto the existing config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tabsNoReplacement tab set: [{id?, name, order?}]. Keep ids to preserve/rename tabs; omit id to add; drop to remove.
labelNoNew name (optional; checked for uniqueness).
styleNoStyle overrides, e.g. {width, background_color} (merged).
footerNoFooter config overrides (merged).
dashboardIdYesThe dashboard (report) ID.
descriptionNoNew description (optional).
tabsEnabledNoShow/hide the tab bar.
tabsPositionNoTab bar position: "left" or "top".
Behavior5/5

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

Beyond the annotation readOnlyHint=false, the description discloses the tabs replacement behavior (including destructive deletion of widgets), the merging of footer/style, and required permissions. This provides comprehensive behavioral context.

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 approximately 150 words, well-structured with clear explanations of each updatable aspect. It front-loads the main purpose and elaborates on parameters efficiently, avoiding redundancy.

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?

Given the tool's complexity (8 parameters, nested objects) and no output schema, the description covers permissions, parameter behavior, and cross-tool references. It is nearly complete; only missing an explanation of the return value, which is not required per rubric.

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 description coverage is 100%, so the baseline is 3. The description adds extra value by explaining the tabs replacement semantics (full list required, id usage for rename/add/remove) and merge behavior for footer/style, which goes beyond the 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 'Update a dashboard' and lists specific updatable components (label, description, tabs, footer, style). It distinguishes the tool from sibling update tools (e.g., update_form) by focusing on dashboard-specific properties.

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 specifies prerequisites (readwrite/admin mode and SMARTSUITE_ENABLE_SCHEMA_WRITE=true) and gives guidance on obtaining tab IDs from smartsuite_describe_dashboard. However, it does not explicitly state when not to use this tool or mention alternatives.

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