Skip to main content
Glama
tasklite-net

TaskLite MCP

by tasklite-net
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_item

Creates a new item with all fields in a single request, including title, column values, status, priority, and due date.

Instructions

Create an item (row) with all of its data in one call. cells maps columnId -> value (use get_board_schema for column ids); every cell is saved with the row. Use set_cell only for later edits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTags as an array of strings
cellsNoCell values keyed by column id: { "<columnId>": value }. Scalars, { amount, currency } for currency, { relatedItemIds: [...] } for relations
titleYesItem title, shown as the row name
statusNoStatus value (todo, in_progress, done, or a value from the board's status options)
boardIdYesBoard id (from list_boards / create_board)
dueDateNoISO date
priorityNoPriority: low, medium, high or urgent
projectIdYesProject id (from list_projects / create_project)
descriptionNoFree-text description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.13.0
    • addedInput schema / properties / boardId / description
      Added value: +"Board id (from list_boards / create_board)"
    • addedInput schema / properties / cells / description
      Added value: +"Cell values keyed by column id: { \"<columnId>\": value }. Scalars, { amount, currency } for currency, { relatedItemIds: [...] } for relations"
    • addedInput schema / properties / description / description
      Added value: +"Free-text description"
    • addedInput schema / properties / priority / description
      Added value: +"Priority: low, medium, high or urgent"
    • addedInput schema / properties / projectId / description
      Added value: +"Project id (from list_projects / create_project)"
    • addedInput schema / properties / status / description
      Added value: +"Status value (todo, in_progress, done, or a value from the board's status options)"
    • addedInput schema / properties / tags / description
      Added value: +"Tags as an array of strings"
    • addedInput schema / properties / title / description
      Added value: +"Item title, shown as the row name"
  2. First observedv0.7.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint false, destructiveHint false), the description adds behavioral details: it performs a single call that saves all cells with the row, and it distinguishes this from set_cell, which is for later updates. This gives the agent a better understanding of the tool's execution model.

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 concise (two sentences) and front-loaded with the primary purpose. It avoids redundant language and packs essential guidance (cells mapping, set_cell distinction) into a small space without losing clarity.

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 create operation with no output schema, the description covers the key aspects: creation, the cells map, and the alternative for later edits. It does not mention return values, which is acceptable given the absence of an output schema, and the required parameters are clearly defined in the schema.

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?

The schema already describes each parameter, but the description adds value by explaining the 'cells' parameter more operationally (use get_board_schema for column ids) and emphasizing that every cell is saved in the same call. This goes beyond the schema's basic property descriptions.

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 clearly states the action ('Create an item') and the resource ('item (row)'), and it distinguishes the tool from alternatives like set_cell by noting that all data is saved in one call. It also references get_board_schema for column ids, which is a specific usage hint.

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 explicitly says 'Use set_cell only for later edits,' which provides a clear alternative and when-not-to-use guidance. It also explains how to use the 'cells' parameter with get_board_schema, offering operational context for a key parameter.

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