Skip to main content
Glama

create_todo

Create a Planner ToDo as a personal task or attach it to an issue. Specify title, priority, due date, and assignee.

Instructions

Create a Planner ToDo. Omit attachedTo for a personal ToDo, or pass attachedTo.type=issue with project and identifier for an issue action item. Omit owner to use the authenticated user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesa string that will be trimmed
descriptionNoToDo description in markdown.
ownerNoa string that will be trimmed
dueDateNoDue date as Unix timestamp in milliseconds.
priorityNoPriority. Default: no-priority.
visibilityNoVisibility. Default: private for personal ToDos, public for issue ToDos.
attachedToNoAttachment target. If omitted, creates a personal ToDo.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesThe successful tool result. The same value is also serialized as JSON in the text content for clients that do not read structuredContent.
warningsNoOptional agent-visible warnings about degraded result fidelity. Omitted when the server returned the documented happy-path payload.
Behavior4/5

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

Annotations already indicate readOnlyHint=false (write operation) and non-destructive. The description adds useful context about default owner behavior and attachment semantics, enhancing transparency without contradicting annotations.

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 extremely concise with two sentences that front-load the purpose and provide actionable usage details. No wasted words.

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?

Given the presence of an output schema, the description adequately explains creation semantics. It covers personal vs. issue attachment and owner default, but does not mention error conditions or permissions, which are minor gaps for a creation tool.

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 description adds meaning beyond the schema by explaining how to use attachedTo for personal vs. issue todos and the effect of omitting owner. Schema coverage is 100%, so baseline is 3, but the description enhances usability.

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 a Planner ToDo' and distinguishes between personal and issue-attached variants. It uses specific verb-resource pairing and differentiates from siblings like create_issue or create_document.

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 provides explicit guidance on when to omit attachedTo for personal todos and when to include it for issue action items. It also explains the owner default. However, it does not explicitly exclude alternative tools or state prerequisites.

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/dearlordylord/huly-mcp'

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