Motion MCP Server

motion_search

Searches Motion tasks and projects by text query. Supports filtering by workspace and result limit.

Instructions

Search Motion tasks and projects by query

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "operation": "<operation>"
    },
    "name": "motion_search"
  }
}

Input Schema

Name	Required	Description
`operation`	Yes	Operation to perform
`query`	No	Search query (required)
`searchScope`	No	What to search (default: both)
`workspaceId`	No	Workspace ID to limit search
`workspaceName`	No	Workspace name (alternative to workspaceId)
`limit`	No	Maximum number of results

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0May 12, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are present, so the description carries the burden of behavioral disclosure. It only says 'Search', which suggests a read-only lookup, but it does not describe return format, pagination, defaults, auth needs, or other important operational behavior.

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 clear sentence with no filler words. It is front-loaded and easy to parse, earning high marks for conciseness even though it is minimal.

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?

Despite a rich schema, the tool has no output schema and no annotations, so the one-sentence description leaves significant gaps such as return value shape, default searchScope behavior, and the inconsistency around the required query parameter. The description is minimally viable but not fully contextual.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds no extra semantic detail beyond the schema; it only names 'query' as the search mechanism, while the schema already documents each parameter fully.

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 uses the specific verb 'Search' and names the resource ('Motion tasks and projects'), making the tool's core purpose clear. It implicitly differentiates from sibling tools like motion_tasks and motion_projects by covering both entities, though it does not explicitly call out alternatives.

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 usage: an agent should use this tool when searching tasks and projects by query. However, it provides no explicit guidance about when to prefer sibling tools or when not to use this tool, so the usage context is only partially stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server