Skip to main content
Tool names are exposed as snake case (for example bar_chart).

Public chart tools

ToolPurposeStatus
bar_chartCreate or update bar/column chartsAvailable
line_chartCreate or update line/index chartsAvailable
area_chartCreate or update area/100% area chartsAvailable
waterfall_chartCreate or update waterfall chartsAvailable
combined_chartCreate or update combined bar/line chartsAvailable
pie_donut_chartCreate or update pie/donut chartsAvailable
scatter_bubble_chartCreate or update scatter/bubble chartsAvailable
mekko_chartCreate or update mekko/marimekko chartsAvailable
dumbbell_chartCreate or update dumbbell chartsAvailable

Public modification and asset tools

ToolPurposeStatus
change_active_chart_rulesReplace all chart rules for an assetAvailable
change_active_chart_annotationsReplace all chart annotations for an assetAvailable
fetch_latest_assetFetch latest asset state from an assetIdAvailable
get_project_changesGet commit diff from assetCommit to latestAvailable
submit_feedbackSend tool/user feedback metadataAvailable

Public but not implemented

ToolPurposeStatus
tableCreate table assetsNot implemented
ganttCreate gantt assetsNot implemented

Private tool

ToolPurposeStatus
push_assetInternal fullscreen editor push/update flowPrivate (not for normal agent usage)

Not currently exposed

These methods exist in code but are not registered as MCP tools:
  • create_default_chart_with_data
  • update_sheet_data
  • update_chart_data
  • update_theme
  • get_chart_as_png

Response pattern for chart tools

Most chart creation/update tools return:
  • structuredContent.assetId
  • structuredContent.assetCommit
  • structuredContent.exportGuideUrl
  • structuredContent.warnings (when present)
They also return a chart screenshot and chart project payload metadata.

Input validation rules

  • Tool schemas reject unknown properties
  • Discriminated unions must use valid type fields such as annotationType, ruleType, and chart-specific union type values
  • Invalid schemas return MCP tool errors
If you change core chart type families or orientation, create a new asset instead of reusing the same assetId.