kintone MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Update General Settings

kintone-update-general-settings

Update a kintone app's general settings in the pre-live environment, including name, icon, theme, comments, and more. Deploy the app to apply the changes to production.

Instructions

Update the general settings of a kintone app. Changes are made to the pre-live environment, which is a temporary storage area where app information is saved before deployment. To reflect changes to the production environment, execute the kintone-deploy-app tool after this tool.

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": {
      "app": "<app>"
    },
    "name": "kintone-update-general-settings"
  }
}

Input Schema

Name	Required	Description
`app`	Yes	The ID of the app to update (numeric value as string)
`icon`	No	The app icon configuration
`name`	No	The app name (1-64 characters)
`theme`	No	The design theme
`revision`	No	Expected revision number for optimistic locking
`titleField`	No	The record title field settings
`description`	No	The app description (up to 10,000 characters)
`enableComments`	No	Whether to enable record comments
`numberPrecision`	No	The numeric calculation precision settings
`enableThumbnails`	No	Whether to enable thumbnail display
`enableBulkDeletion`	No	Whether to enable bulk deletion of records
`enableDuplicateRecord`	No	Whether to enable the reuse record feature
`firstMonthOfFiscalYear`	No	The first month of the fiscal year (1-12)
`enableInlineRecordEditing`	No	Whether to enable inline editing in record list

Output Schema

Name	Required	Description	Default
`revision`	Yes	The revision number after the update

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv1.9.3Aug 26, 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 / properties / icon / anyOf

Removed value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "key": {
-        "description": "The icon key for PRESET type",
-        "type": "string"
-      },
-      "type": {
-        "const": "PRESET",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "key"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "file": {
-        "additionalProperties": false,
-        "description": "The file information for FILE type",
-        "properties": {
-          "fileKey": {
-            "description": "The file key for uploaded icon",
-            "type": "string"
-          }
-        },
-        "required": [
-          "fileKey"
-        ],
-        "type": "object"
-      },
-      "type": {
-        "const": "FILE",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "file"
-    ],
-    "type": "object"
-  }
-]

addedInput schema / properties / icon / oneOf

Added value: +[
+  {
+    "properties": {
+      "key": {
+        "description": "The icon key for PRESET type",
+        "type": "string"
+      },
+      "type": {
+        "const": "PRESET",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "key"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "file": {
+        "description": "The file information for FILE type",
+        "properties": {
+          "fileKey": {
+            "description": "The file key for uploaded icon",
+            "type": "string"
+          }
+        },
+        "required": [
+          "fileKey"
+        ],
+        "type": "object"
+      },
+      "type": {
+        "const": "FILE",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "file"
+    ],
+    "type": "object"
+  }
+]

addedInput schema / properties / icon / type
```
Added value: +"object"
```
removedInput schema / properties / numberPrecision / additionalProperties
```
Removed value: -false
```

removedInput schema / properties / titleField / anyOf

Removed value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "selectionMode": {
-        "const": "AUTO",
-        "type": "string"
-      }
-    },
-    "required": [
-      "selectionMode"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "code": {
-        "description": "The field code for MANUAL selection mode",
-        "type": "string"
-      },
-      "selectionMode": {
-        "const": "MANUAL",
-        "type": "string"
-      }
-    },
-    "required": [
-      "selectionMode",
-      "code"
-    ],
-    "type": "object"
-  }
-]

addedInput schema / properties / titleField / oneOf

Added value: +[
+  {
+    "properties": {
+      "selectionMode": {
+        "const": "AUTO",
+        "type": "string"
+      }
+    },
+    "required": [
+      "selectionMode"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "code": {
+        "description": "The field code for MANUAL selection mode",
+        "type": "string"
+      },
+      "selectionMode": {
+        "const": "MANUAL",
+        "type": "string"
+      }
+    },
+    "required": [
+      "selectionMode",
+      "code"
+    ],
+    "type": "object"
+  }
+]

addedInput schema / properties / titleField / type
```
Added value: +"object"
```

changedOutput schema / $schema

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

First observedv1.4.0May 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the full behavioral disclosure burden. It clearly states that the update modifies a temporary pre-live area, not the live production environment, and that deployment is required for production impact. This is a key side-effect. It does not mention permissions or partial-update behavior, but the schema's revision parameter hints at optimistic locking.

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 with no wasted words. It front-loads the primary purpose, then explains the critical pre-live environment detail and the required follow-up deploy action. Every sentence earns its place.

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 14-parameter tool, the description covers the most important contextual nuance: the pre-live staging behavior and the need for a subsequent deploy. The schema handles all parameter documentation, and an output schema is indicated, so return-value details are not needed. A minor improvement would be noting that unspecified settings remain unchanged, but this is not essential.

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?

All parameters have descriptive text in the input schema, giving 100% schema coverage. The description adds no extra parameter-level meaning, so the baseline of 3 is appropriate.

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 a specific verb and resource: 'Update the general settings of a kintone app.' It clearly distinguishes this tool from sibling tools like kintone-update-form-fields, kintone-update-form-layout, and kintone-update-records by focusing on general settings, and the pre-live environment detail further sharpens the scope.

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?

The description gives explicit sequential guidance: changes go to the pre-live environment, and to affect production you must then execute kintone-deploy-app. This tells the agent when to use this tool and what to do after, but it does not explicitly compare against alternative update tools for non-general settings.

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