hex-dashboard-mcp

create_cell

Add a code, SQL, or markdown cell to a Hex project, specifying content, type, and optional location for insertion.

Instructions

Create a new cell in a Hex project.

cell_type: CODE | SQL | MARKDOWN source: the cell's source code / SQL / markdown content label: optional display label for the cell insert_after_cell_id: optional cell ID to insert after (otherwise appends to end) data_connection_id: required for SQL cells — the Hex data connection UUID

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "cell_type": "<cell_type>",
      "source": "<source>"
    },
    "name": "create_cell"
  }
}

Input Schema

Name	Required	Description	Default
`label`	No
`source`	Yes
`cell_type`	Yes
`project_id`	Yes
`data_connection_id`	No
`insert_after_cell_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It discloses the append-to-end behavior for insert_after_cell_id and the conditional requirement for data_connection_id, but it lacks important behavioral context such as whether the cell is automatically executed, permissions needed, or error semantics. This is a moderate gap.

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 concise and well-structured: a one-sentence purpose statement followed by a bullet-style parameter list. Every line adds value, and there is no redundant or extraneous text.

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?

The description covers most parameter semantics and placement behavior, but it omits guidance on sourcing project_id and does not clarify whether creating a cell triggers execution. Given the presence of run_project and run_and_wait siblings, this missing execution context is a notable gap, though the output schema reduces the need to explain return values.

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?

Despite 0% schema description coverage, the description explains the meaning and allowed values for five of six parameters, including the cell_type enum values, the purpose of data_connection_id, and the optionality of label and insert_after_cell_id. However, it omits explicit documentation of project_id, a required parameter, and does not provide value formats for all IDs.

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 states 'Create a new cell in a Hex project' with a specific verb and resource, clearly distinguishing it from siblings like update_cell_source, delete_cell, and get_cell_source. This is a precise and unambiguous purpose statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides some contextual guidance, such as 'data_connection_id is required for SQL cells' and insert placement semantics, but it does not explicitly state when to use this tool versus alternatives like update_cell_source or delete_cell. The usage context is implied rather than explicitly contrasted.

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

Deploy Server