kintone MCP Server

Official

Overview Schema Source Related Servers Score Discussions Admin

Update Statuses

kintone-update-statuses

Update multiple kintone record statuses at once by specifying process management actions, assignees, and revision checks, for up to 100 records.

Instructions

Update status of multiple records in a kintone app. Requires process management feature to be enabled. Maximum 100 records can be updated at once.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`app`	Yes	The ID of the app (numeric value as string)
`records`	Yes	Array of records to update status (min 1, max 100). Each record contains id, action, and optionally assignee and revision.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`records`	Yes	Array of updated record information

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 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 / records / items / additionalProperties
```
Removed value: -false
```

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

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It does disclose a feature prerequisite and the 100-record limit, which are useful. However, it does not mention permissions, whether updates are atomic across the batch, or what happens on partial failure; schema text covers action/revision errors, but the free-text description remains thin for a mutating workflow tool.

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, no filler, with the core action first followed by the two most decision-relevant constraints. 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 two-parameter tool with a rich input schema and an output schema, the description covers the essential context: what it does, the prerequisite, and the batch ceiling. It is not fully complete because it doesn't name alternatives or side-effect behavior, but the structured fields compensate for most gaps.

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 parameters are already fully documented in the schema. The description adds no parameter meaning beyond what the schema already provides ('100 records' repeats maxItems). Baseline 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 opens with a specific verb and resource: 'Update status of multiple records in a kintone app.' The word 'status' clearly distinguishes this from sibling tools like kintone-update-records, and the process-management requirement reinforces its distinct workflow purpose.

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 gives an important precondition (process management must be enabled) and a batch limit, but it never explicitly says when to choose this tool over kintone-update-records or when status updates are not appropriate. Usage context is implied by the name and 'status' wording rather than stated.

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