Skip to main content
Glama

yg_task_create

Create a task in a column. Define title, description, assignees, deadline, subtasks, and checklists.

Instructions

Create a task in a column.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colorNo
titleYes
archivedNo
assignedNoUser ids to assign.
columnIdYes
deadlineNoms epoch or ISO date.
subtasksNoSubtask (task) ids.
completedNo
checklistsNoChecklists, each { title, items: [{ title, isCompleted }] }.
descriptionNoTask description. RENDERED AS HTML, not markdown and not plain text — newlines are ignored and plain text collapses into one wall of text in the UI. Use tags: <p> paragraphs, <b> bold, <i> italic, <ul>/<ol> + <li> lists, <br> line break, <a href> links. Example: "<p><b>Goal.</b> Ship it.</p><ul><li>step one</li><li>step two</li></ul>". Reading a task back returns the same HTML.
Behavior2/5

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

The description only states 'Create a task' with no mention of side effects, authorization needs, or failure modes. With no annotations, this is insufficient for behavioral understanding.

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 a single sentence, efficient and front-loaded, but could include more detail without harming conciseness.

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?

With 10 parameters, no output schema, and no annotations, the minimal description leaves significant gaps in understanding the tool's usage and behavior.

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?

The schema provides descriptions for some parameters (e.g., description, deadline, assigned), but the tool description itself adds no parameter meaning. Baseline 3 due to 50% schema coverage.

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 task in a column' clearly states the verb and resource, but does not differentiate from sibling tools like yg_task_update or yg_tasks_list.

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 provided on when to use this tool versus alternatives, nor any prerequisites or context for selection.

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/skiddgoddamn/yougile-mcp'

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