Skip to main content
Glama

Create an item or subitem

plaky_create_item

Create a new item or subitem on a board, specifying group and initial field values by key or title.

Instructions

Create a new item (row) on a board, or a subitem when parentId is set. Place it in a group via groupId or groupTitle (defaults to the first group). Set initial field values via fields: an object keyed by field key (e.g. "status-1") or field title (e.g. "Status"). Value formats by field type — String/RichText: "text"; Number: 13.4; Date: "2026-01-02T18:10:15.254Z"; Timeline: {start, end}; Status: "To do" or label id "1"; Tag: ["Product","HR"] or ids; Link: "https://..." or {url, displayText}; Person: {users:[{id}|{email}], teams:[{id}|{title}]}. Call plaky_get_board first to discover available fields and allowed values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoItem title. Defaults to "New Item" / "New Subitem".
fieldsNoInitial field values keyed by field key or title. See tool description for value formats.
boardIdYesUnique board identifier.
groupIdNoId of the group to create the item in.
spaceIdYesUnique space identifier.
parentIdNoIf set, creates a subitem under this parent item id instead of a top-level item.
groupTitleNoTitle of the group to create the item in (used if groupId is omitted).
Behavior3/5

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

No annotations, so description carries the burden. It indicates a write operation (create) but lacks details on failure modes, rate limits, or authentication needs. However, it does not contradict any unstated annotations.

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 informative and well-structured, starting with the core purpose. It is not excessively long, though some redundancy exists (e.g., explaining parentId in both description and schema).

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

Completeness3/5

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

No output schema, so the description should explain return values, but it does not mention what is returned (e.g., created item ID). The guidance on plaky_get_board is helpful, but the gap in output info detracts from completeness.

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 coverage is 100%, baseline 3. The description adds significant value by detailing value formats for fields and default behavior, exceeding the schema's minimal 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 tool creates a new item or subitem, specifying the verb (create), resource (item/subitem), and condition (parentId). It distinguishes from sibling tools like update tools.

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 advises calling plaky_get_board first to discover fields and values, setting a clear prerequisite. It implies alternatives (update tools) but does not explicitly state when not to use this tool.

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

Install Server

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/pavlealeksic/plaky-mcp'

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