Subo

Update a block

update_block

Update one block in place. Only the fields you pass change. Renaming a block does NOT rewrite the [Name] references other blocks make to it — fix those yourself, then validate_script.

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>",
      "block_id": "<block_id>"
    },
    "name": "update_block"
  }
}

Input Schema

Name	Required	Description
`max`	No
`min`	No
`name`	No
`type`	No
`color`	No
`scale`	No
`prompt`	No
`upload`	No
`options`	No
`section`	No
`block_id`	Yes	Block id, from get_script.
`position`	No
`required`	No
`continue_`	No
`hide_when`	No
`image_url`	No
`show_when`	No
`project_id`	Yes	Project id, from list_projects or create_project.
`rank_top_n`	No
`action_kind`	No
`answer_style`	No
`precondition`	No
`when_correct`	No
`action_config`	No
`text_analysis`	No
`thumbnail_url`	No
`when_incorrect`	No
`randomize_options`	No
`calculated_formula`	No
`correct_answer_ids`	No
`correct_answer_index`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 10, 2026

addedInput schema / $defs / UploadSchema

Added value: +{
+  "description": "A `file_upload` block's rules. Every field is optional: images and documents,\none file, required, up to the community's plan limit.",
+  "properties": {
+    "categories": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Categories"
+    },
+    "max_bytes": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Max Bytes"
+    },
+    "max_files": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Max Files"
+    },
+    "min_files": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Min Files"
+    }
+  },
+  "title": "UploadSchema",
+  "type": "object"
+}

addedInput schema / properties / upload

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/UploadSchema"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

Changed4 schema fields changedOct 15, 2026

changedInput schema / $defs / ActionConfigSchema / properties / fire_scope / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "respondent",
+      "session"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / $defs / BlockOptionSchema / properties / anchor_position / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "const": "last",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / $defs / ContinueSchema / properties / after / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "pause",
+      "click"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / $defs / ContinueSchema / properties / pause / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "minimum": 0,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

Changed1 schema field changedOct 6, 2026

addedInput schema / properties / text_analysis

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Text Analysis"
+}

First observedOct 5, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations only cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description carries the rest — and it delivers two real disclosures: this is a partial/PATCH-style update ("Only the fields you pass change") and renaming does not cascade to `[Name]` references in other blocks. That second point is a non-obvious side effect an agent could not infer from the schema or annotations.

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?

Two sentences, zero filler, and the core operation is front-loaded before the caveat and the follow-up step. Every clause carries information the agent needs.

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 mutation tool with 31 mostly-undocumented parameters and no output schema, the definition is thinner than the complexity warrants — nothing tells the agent which fields apply to which block type or what a successful response looks like. It does cover the highest-risk gotcha (broken `[Name]` references) and the validate_script follow-up, which keeps it at minimum viable rather than inadequate.

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

Parameters2/5

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

With 31 parameters and only 6% schema description coverage, the description must compensate and largely does not — it explains none of the block-type-specific fields (scale, upload, options, show_when/hide_when, action_config, correct_answer_ids, etc.). Its one contribution, "only the fields you pass change," does tell the agent that the 29 optional params are an additive patch set, which is meaningful but far short of the coverage gap.

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?

"Update one block in place" states a specific verb (update) and resource (a single block), which implicitly separates it from add_block/delete_block by cardinality and operation. It is clear but never names a sibling alternative explicitly, so it stops short of the top mark.

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 implies the usage context (editing an existing block) and prescribes a follow-up step — fix `[Name]` references yourself, then validate_script — which is genuine workflow guidance. It gives no explicit when-not guidance and never contrasts with add_block for creating new blocks, so the routing decision is only implied.

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

All Subo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.