Skip to main content
Glama

create_habits

Create single or multiple habits in TickTick with custom settings for color, goal, reminders, and repeat rules. Simplify habit tracking by batch-adding daily or weekly routines.

Instructions

Create one or more habits in TickTick.

Supports both single habit and batch creation. For a single habit, pass a dictionary directly. For multiple habits, pass a list of dictionaries.

Args: habits: Habit dictionary or list of habit dictionaries. Each habit must contain: - name (required): Habit name (max 1000 characters) - color (optional): Hex color code, e.g. "#4D8CF5" - type (optional): Habit type, e.g. "Boolean" - goal (optional): Numeric goal, default 1.0 - step (optional): Numeric step value - unit (optional): Unit of the goal, e.g. "Count" - repeat_rule (optional): Recurrence rule, e.g. "RRULE:FREQ=DAILY;INTERVAL=1" - reminders (optional): List of reminder trigger strings - encouragement (optional): Encouragement message - status (optional): Habit status

Examples: # Single boolean habit, repeated daily { "name": "Read", "color": "#4D8CF5", "type": "Boolean", "goal": 1.0, "repeat_rule": "RRULE:FREQ=DAILY;INTERVAL=1" }

# Multiple habits
[
    {"name": "Read", "repeat_rule": "RRULE:FREQ=DAILY;INTERVAL=1"},
    {"name": "Exercise", "repeat_rule": "RRULE:FREQ=WEEKLY;BYDAY=MO,WE,FR"}
]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
habitsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states that habits are created, without mentioning side effects, validation behavior, error handling, or required authentication. 'Create' implies mutation but lacks depth about what happens on failures or partial batch successes.

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?

Although longer than a terse description, every sentence earns its place by documenting fields and providing examples. The structure with 'Args' list and separate examples is well-organized and front-loaded with a clear summary. No fluff.

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

Completeness5/5

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

Given the minimal schema and no annotations, the description thoroughly covers all parameter semantics and examples for both single and batch creation. It is complete enough for an agent to understand how to invoke the tool correctly. The presence of an output schema means return values need not be described.

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

Parameters5/5

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

The input schema provides only a generic 'habits' field with no structure, while the description compensates fully by listing required and optional fields, types, formats (e.g., hex color, RRULE), and defaults. The examples further clarify correct usage, making the parameter meaning explicit.

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 'Create one or more habits in TickTick,' identifying the specific verb (create) and resource (habits). It distinguishes itself from sibling tools like create_tasks and create_project by the resource and the explicit batch creation capability.

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 gives clear context on how to use the tool: supports both single dict and list for batch creation, with examples. It does not explicitly mention when not to use it or contrast with alternatives, but the usage pattern is unambiguous.

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/Code-MonkeyZhang/ticktick-mcp-enhanced'

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