Skip to main content
Glama

motion_tasks

Manage Motion tasks: create, read, update, delete, move, unassign, and list uncompleted tasks, with filters for status, due date, priority, labels, and assignee.

Instructions

Manage Motion tasks - supports create, list, get, update, delete, move, unassign, and list_all_uncompleted operations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoTask name (required for create, optional for list as case-insensitive substring search)
limitNoMaximum number of tasks to return (for list and list_all_uncompleted)
labelsNoFilter by labels (for list). Array of label names
statusNoFilter by status (for list). Single string or array of strings (e.g., ["Todo", "Completed"]). Without status or includeAllStatuses, only active (non-resolved) tasks are returned. Use motion_statuses to list valid values per workspace.
taskIdNoTask ID (required for get/update/delete/move/unassign)
dueDateNoDue date (for create/update) or filter (for list, filtered client-side — returns tasks due on or before this date). Date-only values are stored as end-of-day UTC. Format: YYYY-MM-DD or relative like 'today', 'tomorrow'
assigneeNoFilter by assignee name, email, or 'me' shortcut (for list and list_all_uncompleted). Resolved to an ID automatically
durationNoMinutes (as number) or 'NONE'/'REMINDER' (as string)
priorityNoFilter by priority level (for list, filtered client-side): ASAP, HIGH, MEDIUM, LOW
operationYesOperation to perform
projectIdNoFilter by project (for list)
assigneeIdNoFilter by assignee (for list/list_all_uncompleted), set assignee (for create/update), or reassign (for move)
descriptionNoTask description
projectNameNoProject name (alternative to projectId)
workspaceIdNoFilter by workspace (for list)
autoScheduledNoAuto-scheduling configuration. Can be either: - A schedule name string: "Work Hours" (simple, no start date) - An object for full control: {"schedule": "Work Hours", "startDate": "2025-03-05", "deadlineType": "SOFT"} When the user specifies a start date, you MUST use the object form. Use motion_schedules to see available schedule names.
workspaceNameNoFilter by workspace name (for list)
targetWorkspaceIdNoTarget workspace ID (required for move operation). Move transfers a task between workspaces — project-level targeting is not supported by the Motion API.
includeAllStatusesNoWhen true, returns tasks across all statuses including completed/resolved (for list). Cannot be combined with status filter.
Behavior2/5

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

With no annotations provided, the description was expected to disclose behavioral traits, but it only lists operation names without explaining side effects, permissions, rate limits, or results. Destructive operations like delete or move are not given any cautionary or contextual detail.

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, front-loaded sentence that concisely names the resource and the supported operations. Every element is informative, and there is no redundancy or filler.

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?

This is a complex, 8-operation tool with 19 parameters and no annotations or output schema. The brief description leaves operation-specific behaviors, return formats, and safety warnings entirely to the schema, which is insufficient for a tool this broad.

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 covers 100% of the 19 parameters with detailed descriptions, so the baseline of 3 applies. The description itself adds no parameter semantics beyond saying operations are supported, which does not exceed the schema's coverage.

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 manages Motion tasks and lists all eight supported operations (create, list, get, update, delete, move, unassign, list_all_uncompleted). This distinguishes it from sibling tools focused on schedules, statuses, projects, and other domains.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for task operations via 'Manage Motion tasks' and the operation list, but it does not explicitly address when to prefer this tool over siblings like motion_search or motion_schedules, nor does it state exclusions or prerequisites. Guidance is implied rather than explicit.

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/mattdkonig/motion-mcp-server'

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