Skip to main content
Glama

tasks_create

Creates a new task with subject, optional assignee, due date, project association, and subtask linking for managing work items.

Instructions

Add a new task to a project or as a standalone task.

Creates a task with subject, optional description, assignee, due date, and project association.

Workflow tips:

  • Subject is required (task title)

  • Assign to a user with assignee_id

  • Associate with a project using project_id

  • Create subtasks using parent_task_id

  • Set due_date for deadline tracking

  • Tasks default to not done (done = 0)

Common use cases:

  • Create project task: { "subject": "Review proposal", "project_id": 123, "assignee_id": 456 }

  • Create subtask: { "subject": "Research options", "parent_task_id": 789 }

  • Create with due date: { "subject": "Send report", "due_date": "2024-12-31" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subjectYesTask subject/title
project_idNoID of the project this task belongs to
assignee_idNoID of the user assigned to this task
parent_task_idNoID of the parent task if this is a subtask
doneNoWhether the task is done (0 = not done, 1 = done)
due_dateNoDue date in YYYY-MM-DD format
descriptionNoTask description
Behavior3/5

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

No annotations are provided, so the description carries the disclosure burden. It explains creation behavior, default value for 'done', and optional fields. It doesn't mention potential response format, permission requirements, or side effects beyond creation. Adequate but not rich.

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 well-structured with sections (workflow tips, common use cases) and includes helpful examples. It is slightly longer than necessary but every part adds value. No redundant information.

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 7 parameters and no output schema or annotations, the description covers creation intent, defaults, and parameter relationships. It could mention the resulting resource (e.g., returns created task) but is largely complete for a creation tool.

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 has 100% description coverage, but the description adds significant value with workflow tips and concrete examples for common parameter combinations (e.g., project task, subtask, due date). This goes beyond the schema's descriptions.

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 the action ('Add a new task') and the resource ('task'). It distinguishes from sibling tools like tasks_delete, tasks_get, tasks_list, and tasks_update by specifying creation. The scope (project or standalone) is also defined.

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 workflow tips and common use cases, guiding the agent on parameter usage. However, it lacks explicit when-to-use vs alternatives (e.g., vs tasks_update). It implicitly covers creation scenarios well.

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/iamsamuelfraga/mcp-pipedrive'

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