Skip to main content
Glama
kintone

kintone MCP Server

Official
by kintone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Deploy App Settings

kintone-deploy-app

Deploy kintone app settings from pre-live to production asynchronously; verify progress with the kintone-get-app-deploy-status tool.

Instructions

Deploy app settings from pre-live to production environment on kintone. This is an asynchronous API - use kintone-get-app-deploy-status tool to check deployment progress.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appsYesList of apps to deploy (minimum 1, maximum 300 apps). Each entry must have app (which app to deploy).
revertNoIf true, revert changes instead of deploying (default: false)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesDeployment status message

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.11.0
    • changedInput schema / properties / apps / description
      Previous value: -"List of apps to deploy (minimum 1, maximum 300 apps)"New value: +"List of apps to deploy (minimum 1, maximum 300 apps). Each entry must have app (which app to deploy)."
    • changedInput schema / properties / apps / items / properties / app / description
      Previous value: -"The ID of the app to deploy (numeric value as string)"New value: +"Required. The ID of the app to deploy (numeric value as string)"
    • removedInput schema / properties / apps / items / required
      Removed value: -[
-  "app"
-]
  2. Changed3 schema fields changedv1.9.3
    • 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 / apps / 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"
  3. Addedv1.9.1
  4. Removedv1.9.0
  5. First observedv1.4.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and usefully discloses the asynchronous nature of the operation and the follow-up status tool. It does not cover permissions, reversibility semantics (the schema's revert flag is never explained), or rate/batch behavior, but the async disclosure is a substantive behavioral fact.

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 tight sentences with zero waste, and the core action is front-loaded before the async caveat.

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?

An output schema exists so return values need not be described, and the async workflow guidance covers the main operational gap. Missing only peripheral details such as permissions or revert semantics, which the schema partially covers.

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 both apps and revert. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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 and resource with scope: 'Deploy app settings from pre-live to production environment on kintone.' This clearly separates it from sibling read/update tools. It does not explicitly contrast with near-neighbors like kintone-update-general-settings, but the deploy semantics are distinctive.

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?

Provides clear operational context: it is asynchronous and progress should be tracked via kintone-get-app-deploy-status. This tells the agent what to do after invocation. It lacks explicit when-not-to-use guidance versus other mutation tools, so it stops short of a 5.

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

Deploy Server

Other Tools