Skip to main content
Glama
kanjidoc
by kanjidoc

missive_create_task

Create tasks in Missive as standalone items, as tasked conversations, or as subtasks inside conversations. Requires a title; supports assignment, due dates, and organization settings.

Instructions

Creates a task in Missive (standalone task, tasked conversation, or a subtask inside a conversation). Tasks created via the API appear in the Tasks view, not the Inbox. title is required; organization is required when using team, assignees, or add_users (defaults to MISSIVE_DEFAULT_ORGANIZATION); a subtask requires conversation or references.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamNoTeam ID to assign the task to. For a standalone task, either `team` or `assignees` is required.
stateNoInitial task state: 'todo', 'in_progress', or 'closed'. Defaults to 'todo'.
titleYesTask title (required, max 1000 characters).
due_atNoUnix timestamp for when the task is due.
subtaskNoSet true to create this task as a subtask inside a conversation. Requires `conversation` or `references`.
add_usersNoUser IDs to add to the parent conversation (subtasks only). Requires `organization`.
assigneesNoArray of user IDs to assign the task to. For a standalone task, either `team` or `assignees` is required.
referencesNoMessage references (e.g. email Message-IDs) used to find or create the parent conversation for a subtask, as an alternative to `conversation`.
descriptionNoTask description, plain text (max 10000 characters).
add_to_inboxNoSet true to move the parent conversation to the Inbox for everyone with access (subtasks only).
conversationNoParent conversation ID for a subtask (required when `subtask` is true).
organizationNoOrganization ID. Required when using `team`, `assignees`, or `add_users`. Defaults to MISSIVE_DEFAULT_ORGANIZATION if set.
conversation_subjectNoSubject for the parent conversation when creating it via `references` (only used when a new conversation is created).
Behavior4/5

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

Annotations only have destructiveHint: false. The description adds that tasks appear in Tasks view, not Inbox, and clarifies subtask requirements. It does not contradict annotations and provides useful 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?

Two sentences, no fluff. The first sentence establishes purpose, the second covers key constraints and defaults. Every sentence adds value and is well-structured.

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 no output schema, the description does not explain return values, but it covers all necessary behavioral and parameter context for a create tool. It is complete enough for an agent to use correctly.

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?

Input schema has 100% coverage, baseline 3. The description adds meaning beyond schema by explaining defaults (organization), dependencies (subtask requires conversation/references), and usage of parameters like add_users and conversation_subject, earning an extra point.

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 tool creates tasks in Missive, specifying three types (standalone task, tasked conversation, subtask). It uses a specific verb-resource combo and distinguishes from sibling tools like missive_create_draft and missive_create_message by focusing on task creation.

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?

Provides context on when to create a subtask vs standalone, and notes required parameters like organization. However, it does not explicitly compare to other create tools or state when not to use this tool, leaving some ambiguity.

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/kanjidoc/missive-mcp'

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