AssetLab

Update form template item

update_form_template_item

DestructiveIdempotent

Update an existing form template item by ID. template_id and item_key are immutable and cannot be changed. Requires form_template_items:write scope.

Input Schema

Name	Required	Description
`id`	Yes	Form template item ID
`label`	No	Question label / prompt
`config`	No	Per-type configuration (e.g. { min, max, unit, multiline })
`options`	No	Choices for single_select / multi_select items
`required`	No	Whether an answer is required
`help_text`	No	Help text shown under the label
`item_type`	No	Item type (section, checkbox, single_select, multi_select, number, text, photo, team_members, signature)
`sort_order`	No	Display order within the template
`visible_when`	No	Conditional-visibility rule referencing another item

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 16, 2026

changedInput schema / properties / item_type / description

Previous value: -"Item type (section, checkbox, single_select, multi_select, number, text, photo)"New value: +"Item type (section, checkbox, single_select, multi_select, number, text, photo, team_members, signature)"

changedInput schema / properties / item_type / enum

Previous value: -[
-  "section",
-  "checkbox",
-  "single_select",
-  "multi_select",
-  "number",
-  "text",
-  "photo"
-]New value: +[
+  "section",
+  "checkbox",
+  "single_select",
+  "multi_select",
+  "number",
+  "text",
+  "photo",
+  "team_members",
+  "signature"
+]

Changed7 schema fields changedOct 7, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / config / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / id / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"

removedInput schema / properties / options / items / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / sort_order / maximum
```
Added value: +9007199254740991
```

changedInput schema / properties / visible_when / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "itemKey": {
-        "type": "string"
-      },
-      "op": {
-        "type": "string"
-      },
-      "value": {}
-    },
-    "required": [
-      "itemKey",
-      "op"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "itemKey": {
+        "type": "string"
+      },
+      "op": {
+        "type": "string"
+      },
+      "value": {}
+    },
+    "required": [
+      "itemKey",
+      "op"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed7 schema fields changedOct 7, 2026

changedInput schema / $schema

Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / config / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```

removedInput schema / properties / id / pattern

Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"

addedInput schema / properties / options / items / additionalProperties
```
Added value: +false
```
removedInput schema / properties / sort_order / maximum
```
Removed value: -9007199254740991
```

changedInput schema / properties / visible_when / anyOf

Previous value: -[
-  {
-    "properties": {
-      "itemKey": {
-        "type": "string"
-      },
-      "op": {
-        "type": "string"
-      },
-      "value": {}
-    },
-    "required": [
-      "itemKey",
-      "op"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "itemKey": {
+        "type": "string"
+      },
+      "op": {
+        "type": "string"
+      },
+      "value": {}
+    },
+    "required": [
+      "itemKey",
+      "op"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed7 schema fields changedOct 7, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / config / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / id / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"

removedInput schema / properties / options / items / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / sort_order / maximum
```
Added value: +9007199254740991
```

changedInput schema / properties / visible_when / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "itemKey": {
-        "type": "string"
-      },
-      "op": {
-        "type": "string"
-      },
-      "value": {}
-    },
-    "required": [
-      "itemKey",
-      "op"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "itemKey": {
+        "type": "string"
+      },
+      "op": {
+        "type": "string"
+      },
+      "value": {}
+    },
+    "required": [
+      "itemKey",
+      "op"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

First observedOct 7, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Adds two genuinely useful facts beyond the annotations: the required form_template_items:write scope and that template_id and item_key are immutable (note these aren't even in the schema). However, with destructiveHint=true and idempotentHint=true already declared, the description never explains the destructiveness — e.g. whether omitted fields are cleared or preserved (partial vs full replace).

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?

Three short sentences, front-loaded with the action, then constraints, then the auth requirement. No filler or repetition.

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?

For a 9-parameter mutation with nested objects and no output schema, the description covers identity, immutability, and auth, but omits the update semantics that matter most given destructiveHint=true. Adequate but with a real gap around partial-update behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 9 parameters, including the enum and nested visible_when/config objects. The description adds nothing about parameter semantics beyond immutability of two fields that aren't in the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource+identifier ('Update an existing form template item by ID'), making it clearly distinct from create_form_template_item and update_form_template. It stops short of naming the sibling it complements, but the resource is unambiguous.

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

Usage Guidelines2/5

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

No when-to-use guidance, no alternatives, and no prerequisites beyond the scope line. An agent must infer from the name that this is the mutation path for an existing item rather than a bulk_update or create path.

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

All AssetLab tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?