Create, update, move, list, and search cards

create_card requires only title; omitted board and column inputs use the documented defaults, so verify and disclose the resolved destination when it was not explicit. Priority defaults to medium. A new card is inserted at the top with sort_order = 0, shifting the existing cards, and the calling Agent is recorded as authorship metadata without changing access. There is no same-column position or reorder parameter; precise ordering requires UI drag-and-drop.

update_card is a field-level patch: omitted fields stay unchanged, and field changes plus a column move may be submitted together. move_card delegates to that same behavior. Its schema requires only cardId, but runtime also requires at least one of columnId or columnName.

A destination column is always resolved inside the card’s current board, so cross-board move is unsupported. For a cross-board request, create a replacement card on the destination board and delete the old card only after the required confirmation; do not imply that move_card can transfer it.

Use list_cards for board or column scans, optional substring filtering, and pagination; it excludes archived cards. search_cards does title/description substring lookup without wildcard syntax and also excludes archived cards. Direct get_card rejects archived cards as not found. Use the archive-specific UI/API when historical cards are required. Mutations support dry_run, which returns resolved resources and wouldRequireConfirmation without applying the change.

Related actions

arinova.kanban.create_card, arinova.kanban.update_card, arinova.kanban.move_card, arinova.kanban.list_cards, arinova.kanban.search_cards, arinova.kanban.delete_card

Also known as

create task card, update card, move card, reorder card, cross board move, active card search, card dry run

---

Machine-readable Markdown · Knowledge index