kintone MCP Server

Official

Overview Schema Source Related Servers Score Discussions Admin

Get Record Comments

kintone-get-record-comments

Retrieve comments posted on a single kintone record. Fetch up to 10 comments per call and use offset to paginate through older comments.

Instructions

Get comments posted on a single kintone record. The kintone API returns comments for one record at a time; to fetch comments for multiple records, call this tool repeatedly. Up to 10 comments are returned per call; use offset to paginate.

Input Schema

TableJSON Schema

Name	Required	Description
`app`	Yes	The ID of the app that contains the record (numeric value as string)
`limit`	No	Maximum number of comments to retrieve (1-10, default: 10 by kintone API)
`order`	No	Sort order of comments by createdAt. 'asc' = oldest first, 'desc' = newest first (default: desc)
`offset`	No	Number of comments to skip (default: 0)
`record`	Yes	The ID of the record to retrieve comments from

Output Schema

TableJSON Schema

Name	Required	Description
`newer`	Yes	Whether there are newer comments beyond this page
`older`	Yes	Whether there are older comments beyond this page
`comments`	Yes	Array of comments on the record

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 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"

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.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the API returns comments for one record at a time, caps results at 10 per call, and requires offset for pagination. It also implies read-only behavior through 'Get' and 'returns'. It does not cover error handling, but the key operational behaviors are disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences with no filler, each carrying a distinct piece of information: the resource and scope, the multi-record usage pattern, and pagination limits. There is slight redundancy between 'single' and 'one record at a time,' but the overall structure is tight and front-loaded.

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?

Given 100% schema coverage, an output schema, and no annotations, the description covers the non-obvious operational context an agent needs: the single-record limitation and pagination behavior. It does not mention ordering behavior or error cases, but these are minor given the schema and output schema. The tool is sufficiently complete for correct invocation.

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 description coverage is 100%, so the baseline is 3. The description adds value beyond the schema by explaining the relationship between limit and offset: up to 10 comments are returned per call and offset is used to paginate. This complements the schema's numeric bounds and makes parameter usage clearer.

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 the verb 'Get' and identifies the exact resource: comments on a single kintone record. It clearly states the one-record-at-a-time constraint, which separates this tool from bulk record tools like kintone-get-records and from write tools like kintone-add-record-comment. The scope 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 Guidelines4/5

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

The description gives clear operational context: this tool fetches comments for one record only, and for multiple records the agent must call the tool repeatedly. It does not explicitly name alternative sibling tools, but the use case is distinct enough that this is not a serious gap. No misleading usage guidance is present.

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