Things MCP

Overview Schema Source Related Servers Discussions Admin

things_create_item

Idempotent

Create to-dos, projects, areas, or tags in Things 3 by supplying a unique request ID and title. Add notes, deadlines, scheduling, and status to organize tasks.

Instructions

Create a to-do, project, area, or tag. Supply a unique UUID requestId. Creation of all four kinds is native verified. Local write permission is required and disabled by default.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	Yes
`notes`	No
`title`	Yes
`areaId`	No
`status`	No
`tagIds`	No
`deadline`	No
`collapsed`	No
`projectId`	No
`requestId`	Yes
`parentTagId`	No
`creationDate`	No
`scheduledDate`	No
`completionDate`	No
`cancellationDate`	No
`keyboardShortcut`	No
`modificationDate`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv1.0.2Sep 8, 2026

addedInput schema / properties / areaId

Added value: +{
+  "maxLength": 128,
+  "minLength": 1,
+  "pattern": "^[A-Za-z0-9_-]+$",
+  "type": "string"
+}

addedInput schema / properties / cancellationDate

Added value: +{
+  "anyOf": [
+    {
+      "format": "date-time",
+      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedInput schema / properties / collapsed
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / completionDate

Added value: +{
+  "anyOf": [
+    {
+      "format": "date-time",
+      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedInput schema / properties / creationDate

Added value: +{
+  "format": "date-time",
+  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
+  "type": "string"
+}

addedInput schema / properties / deadline

Added value: +{
+  "anyOf": [
+    {
+      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedInput schema / properties / keyboardShortcut

Added value: +{
+  "maxLength": 1,
+  "type": "string"
+}

addedInput schema / properties / modificationDate

Added value: +{
+  "format": "date-time",
+  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
+  "type": "string"
+}

addedInput schema / properties / parentTagId

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 128,
+      "minLength": 1,
+      "pattern": "^[A-Za-z0-9_-]+$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedInput schema / properties / projectId

Added value: +{
+  "maxLength": 128,
+  "minLength": 1,
+  "pattern": "^[A-Za-z0-9_-]+$",
+  "type": "string"
+}

addedInput schema / properties / scheduledDate

Added value: +{
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

addedInput schema / properties / status

Added value: +{
+  "enum": [
+    "open",
+    "completed",
+    "canceled"
+  ],
+  "type": "string"
+}

addedInput schema / properties / tagIds

Added value: +{
+  "items": {
+    "maxLength": 128,
+    "minLength": 1,
+    "pattern": "^[A-Za-z0-9_-]+$",
+    "type": "string"
+  },
+  "maxItems": 100,
+  "type": "array"
+}

First observedv0.83.0Sep 6, 2026

TDQS

B3.3/5.0

Behavior4/5

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

The annotations already indicate this is a writing, non-destructive, idempotent operation. The description adds valuable behavioral context beyond the annotations: local write permission is required and disabled by default, and requestId must be unique. This meaningfully informs the agent about preconditions and side-effect profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded with the core operation, which is good. However, the sentence 'Creation of all four kinds is native verified' largely restates the first sentence and adds little new value, making it a redundant sentence in an otherwise compact description.

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?

Given the tool's complexity and the large optional parameter set, the description covers the essential entry-point requirements: what can be created, the required requestId, and the permission precondition. It does not cover how parameters should be combined per kind, which limits completeness even though the presence of an output schema reduces the need to describe return values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema description coverage at 0% and 17 parameters, the description carries a heavy burden but only explains requestId uniqueness and indirectly the kind values. It does not clarify semantic relationships such as areaId vs. projectId applicability, status/dates usage, or when fields are appropriate for each item kind, leaving most parameter semantics underspecified.

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 explicitly enumerates the four resource types ('to-do, project, area, or tag'), making the tool's primary function unmistakable. It does not explicitly contrast itself with siblings like things_create_from_template or things_duplicate_item, so it stops short of full sibling differentiation.

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

Usage Guidelines3/5

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

The description gives clear prerequisites: supply a unique UUID requestId and have local write permission enabled, which is necessary because it is disabled by default. However, it does not state when to choose this tool over alternatives such as create_from_template, update_item, or duplicate_item, so guidance on alternatives is missing.

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