Skip to main content
Glama

kaiten_create_automation

Create automated workflows in a Kaiten space by defining triggers, conditions, and actions to streamline card management.

Instructions

Create a new automation in a Kaiten space.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesAutomation name (max 256 chars)
typeNoAutomation type. Default: on_action
actionsYesList of action configurations [{type, data}]. Action types: add_assignee, remove_assignee, move_to_path, move_on_board, add_tag, remove_tags, add_card_users, add_property, add_child_card, add_parent_card, connect_parent_card, remove_card_users, change_asap, add_user_groups, add_size, add_timeline, add_due_date, remove_due_date, add_template_checklists, complete_checklists, sort_cards, add_comment, card_add_sla, card_remove_sla, blocked, unblocked, blocker_added, archive, change_custom_property_value, property_add_to_child_card, change_type, change_service
triggerYesTrigger configuration {type, data}. Trigger types: card_created, card_moved_in_path, comment_posted, card_user_added, responsible_added, card_type_changed, checklists_completed, tag_added, tag_removed, card_state_changed, custom_property_changed, due_date_changed, child_cards_state_changed, checklist_item_checked, due_date_on_date, checklist_item_due_date_on_date, custom_property_date_on_date, blocked, unblocked, blocker_added, all_conditions_met
space_idYesSpace ID
conditionsNoConditions configuration. Top-level: {clause: 'and'|'or', conditions: [...]}. Condition types: tag, target_tag, card_type, new_card_type, updater, path, new_path, card_state, new_card_state, comment, target_custom_property, custom_property, due_date, new_due_date, new_child_cards_state, child_cards_state, checklist_item_text, checklist_item_due_date, checklist_item_checked_state, card_is_request, card_author, block_status, relations, service, size
sort_orderNoSort position of the automation within the space.
source_automation_idNoUUID of an existing automation to copy. When set, the automation is cloned from the source instead of being created from trigger/actions.
Install Server

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral disclosure burden. 'Create a new automation' implies a mutating operation but does not disclose permissions, idempotency, validation behavior, side effects, or the fact that trigger/actions may be ignored when source_automation_id is set. This is a notable transparency gap for a creation 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?

The description is one short, front-loaded sentence with no filler or redundant phrasing. It immediately states the tool's purpose and earns its place efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of nested trigger/actions/conditions objects, the absence of annotations, and no output schema, the description is too thin to fully equip an agent. The schema details parameters well, but the description does not explain return expectations, prerequisites, or the relationship to kaiten_copy_automation, leaving important context missing.

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%, and individual parameter descriptions are rich, including enums for trigger and action types. The description itself adds no parameter-level meaning, so the baseline of 3 applies. It neither helps nor hinders beyond what the schema already provides.

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?

The description uses a specific verb and resource: 'Create a new automation in a Kaiten space.' It clearly identifies the action and target resource, differentiating it from update/delete/list automation tools. However, it does not explicitly distinguish itself from the sibling kaiten_copy_automation, especially since the schema's source_automation_id allows cloning.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives. With siblings like kaiten_copy_automation, kaiten_update_automation, and kaiten_list_automations, an agent receives no exclusions or selection criteria. The only implied usage is 'when you need to create an automation,' which is minimal.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ViktorOgnev/kaiten-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server