Skip to main content
Glama
artiinjooo

Motion MCP Server

by artiinjooo

motion_tasks

Manage Motion tasks: create, update, delete, move, and list tasks with filters by status, assignee, priority, due date, and labels. Also supports unassigning and listing all uncompleted tasks.

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, the description carries the full burden of behavioral disclosure. It only lists operations, omitting important behaviors such as whether operations are destructive (e.g., delete), idempotent, or require special permissions. Critical details like the move operation's workspace-only targeting (documented in schema but not description) are not highlighted.

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, very concise. However, it lacks structure—no bullet points or organization. While brief, it could be more helpful by grouping operations or using structured formatting without adding length.

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 high complexity (19 parameters, 8 operations, no output schema, no annotations), the description is severely incomplete. It does not explain return values, error cases, operation-specific behavior, or how to leverage sibling tools (e.g., motion_statuses). The schema partially compensates, but the tool description leaves significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. However, the tool description adds no value beyond listing operations. It does not explain parameter relationships, such as which parameters are required for each operation or how to combine filters. A dedicated parameter mapping would significantly improve semantics.

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 clearly states the tool manages Motion tasks and lists all supported operations (create, list, get, update, delete, move, unassign, list_all_uncompleted). It uses a specific verb ('Manage') and resource, but does not distinguish it from sibling tools like motion_comments or motion_projects, which also manage task-related entities.

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 on when to use this tool vs alternatives (e.g., motion_search for advanced filtering, motion_statuses for status values). The description does not mention prerequisites, context, or exclusions. Users must infer usage from the listed operations alone.

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/artiinjooo/motion-mcp-server1'

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