hacknplan-mcp

update_design_element

Update design elements in HacknPlan by renaming, editing documentation, re-parenting, or changing type. Preserve existing values by passing current type_id and name.

Instructions

Update a design element (rename, edit documentation, re-parent, change type). type_id and name are required by the API; pass the element's current values to keep them. Use get_design_element first to read them.

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>",
      "element_id": "<element_id>",
      "type_id": "<type_id>",
      "name": "<name>"
    },
    "name": "update_design_element"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`type_id`	Yes
`parent_id`	No
`element_id`	Yes
`project_id`	Yes
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 31, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations, the description must carry the transparency burden. It discloses that type_id and name are required by the API and that passing current values preserves them, implying a partial update behavior. However, it does not mention return values, permission requirements, or side effects of re-parenting, leaving some uncertainty.

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 two sentences, front-loaded with the core action and a concise list of operations, followed by essential usage guidance. Every sentence contributes meaning without unnecessary verbosity.

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?

For a 6-parameter mutation tool with no annotations or output schema, the description covers core semantics, required fields, and a recommended pre-step. It lacks details on return values or error scenarios, but given the straightforward nature of the update, it is reasonably complete.

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 0%, but the description compensates by mapping operations to parameters: rename maps to name, edit documentation to description, re-parent to parent_id, and change type to type_id. It also clarifies the role of required fields. It doesn't explicitly explain project_id and element_id, but these are inferable from context.

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 'Update a design element' and enumerates specific operations (rename, edit documentation, re-parent, change type), making it clear what the tool does and distinguishing it from sibling tools like delete_design_element or get_design_element.

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?

It instructs to call get_design_element first to read current values and explains that type_id and name must be passed with current values to preserve them. This provides clear context on prerequisite steps and how to avoid overwriting fields, though it doesn't explicitly list alternative tools for similar actions.

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

Deploy Server