Skip to main content
Glama

create_task

Add a new task or deliverable to a client project. Specify task details, assignees, due dates, and subtasks.

Instructions

Create a new task/deliverable in a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the task
tasksNoArray of subtask names to create under this task
statusNoTask status - must match exactly a status in your kanban if provided
dueDateNoTask due date (YYYY-MM-DD format)
priorityNoNumeric priority for sorting in kanban
startDateNoTask start date (YYYY-MM-DD format)
assignedToNoEmail addresses of users in the workspace to assign this task to
clientNameYesExact match of a client record in your CRM
descriptionNoTask description
projectNameYesExact name of the project owned by the client to add this task to
customValuesNoMap of custom fields. Keys must match exactly the fields specified in your project settings custom fields setup
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only states the action without covering side effects, permissions, or constraints beyond the input schema. The description adds no behavioral context.

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 a single concise sentence with no fluff. It is front-loaded and earns its place, efficiently conveying the tool's purpose.

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 complexity (11 parameters, no output schema, no annotations), the description is too minimal. It lacks information about return values, error handling, prerequisites, or post-creation behavior, making it incomplete for agent usage.

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 input schema has 100% description coverage, so the description adds little extra meaning. The baseline is 3, and the description does not enhance understanding beyond what the schema already provides.

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 'Create' and the resource 'task/deliverable in a project', making the tool's purpose immediately obvious. It is specific and distinct from sibling tools like 'approve_deliverable' or 'create_project'.

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 is provided on when to use this tool versus alternatives. There are many creation tools among siblings, but no conditions or exclusions are mentioned to help the agent select this tool appropriately.

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/SabryParra/moxie-mcp'

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