Skip to main content
Glama

create_task

Create a task in a Planner bucket: required plan, bucket, and title. Optionally set description, dates, priority, assignments, and categories.

Instructions

Create a new task in a bucket

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTask title
planIdYesPlan ID
bucketIdYesBucket ID where to create the task
priorityNoPriority: 1=urgent, 3=important, 5=medium, 9=low (optional)
assignmentsNoAssignments keyed by user ID. Use null to remove, or plannerAssignment object to add/update.
descriptionNoTask description (optional)
dueDateTimeNoDue date in ISO 8601 format (optional)
startDateTimeNoStart date in ISO 8601 format (optional)
percentCompleteNoPercentage of task completion 0-100 (optional)
appliedCategoriesNoLabels/categories as JSON string with category names as keys and boolean values. To ADD a tag set it to true (e.g., '{"category1":true}'). To REMOVE a tag you MUST set it to false (e.g., '{"category1":false}') — sending {} will NOT remove anything.
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only says 'create', omitting behavioral traits such as validation, side effects, permissions, rate limits, or idempotency. Essential information is missing.

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 a single sentence, very concise. However, it sacrifices informative content for brevity. It is not front-loaded with critical information and contains no structural elements like bullet points or sections.

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

Completeness2/5

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

Given the tool's complexity (10 parameters, nested objects, no output schema, no annotations), the description is insufficient. It does not cover return values, error conditions, or practical usage examples. Sibling tools exist but are not referenced.

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

Parameters3/5

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

Schema description coverage is 100%, so a baseline of 3 is appropriate. The description does not add any value beyond the schema; it does not explain parameter relationships or usage context. The schema descriptions are present but the tool description does not enhance them.

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 'Create a new task in a bucket' clearly states the action (create) and the resource (task) with a location hint. It distinguishes from siblings like create_bucket (bucket creation) and update_task (update). However, it could be more specific about the system (e.g., Planner).

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives like update_task or create_bucket. There are no prerequisites, exclusions, or context provided. The agent must infer from the name alone.

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/Plong-Wasin/planner-mcp'

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