Skip to main content
Glama

motion_tasks

Create, list, get, update, delete, move, unassign, or list all uncompleted tasks in Motion, filtering by workspace, project, assignee, status, priority, due date, labels, and name.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYesOperation to perform
taskIdNoTask ID (required for get/update/delete/move/unassign)
workspaceIdNoFilter by workspace (for list)
workspaceNameNoFilter by workspace name (for list)
projectIdNoFilter by project (for list)
projectNameNoProject name (alternative to projectId)
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.
includeAllStatusesNoWhen true, returns tasks across all statuses including completed/resolved (for list). Cannot be combined with status filter.
assigneeIdNoFilter by assignee (for list/list_all_uncompleted), set assignee (for create/update), or reassign (for move)
assigneeNoFilter by assignee name, email, or 'me' shortcut (for list and list_all_uncompleted). Resolved to an ID automatically
priorityNoFilter by priority level (for list, filtered client-side): ASAP, HIGH, MEDIUM, LOW
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'
labelsNoFilter by labels (for list). Array of label names
nameNoTask name (required for create, optional for list as case-insensitive substring search)
descriptionNoTask description
durationNoMinutes (as number) or 'NONE'/'REMINDER' (as string)
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.
targetWorkspaceIdNoTarget workspace ID (required for move operation). Move transfers a task between workspaces — project-level targeting is not supported by the Motion API.
limitNoMaximum number of tasks to return (for list and list_all_uncompleted)
Behavior2/5

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

No annotations exist, and the description only lists operations without revealing behavioral traits like side effects (creation/deletion/mutation), authentication requirements, rate limits, or data consistency guarantees. For a tool with destructive operations, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but lacks structure. It does not front-load the most critical information (e.g., operation dispatch) or organize content for quick scanning.

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 19 parameters and no output schema, the description fails to explain return values, pagination, or error handling. It leaves significant information gaps that the agent must infer from the schema alone.

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?

Despite 100% schema description coverage, the tool's description adds no value beyond the schema's parameter details. Baseline 3 is appropriate as the schema provides adequate semantic information but the description does not augment it.

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 lists eight specific operations (create, list, get, update, delete, move, unassign, list_all_uncompleted) clearly indicating this tool manages Motion tasks. While 'manage' is broad, the enumerated operations provide clear purpose and distinguish it from sibling tools focused on specific entity types.

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 such as motion_statuses for status values or motion_schedules for scheduling. There are no 'when not to use' instructions or references to sibling tools for context.

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

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