DragApp MCP Server

move_thread

Move an email thread to a different column or board to triage incoming messages and organize team workflows.

Instructions

Move an email thread to a different column or board. Use this to triage emails — e.g. move from Inbox to In Progress, or to a different team's board.

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": {
      "threadId": "<threadId>",
      "newBoardId": "<newBoardId>",
      "newColumnId": "<newColumnId>"
    },
    "name": "move_thread"
  }
}

Input Schema

Name	Required	Description
`position`	No	Position in the target column (0 = top, default: 0)
`threadId`	Yes	The thread/entity ID to move
`newBoardId`	Yes	Target board ID
`newColumnId`	Yes	Target column ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.5Jul 7, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the basic action without mentioning side effects (e.g., whether the move is reversible, permission requirements, or impact on thread visibility). This is insufficient for a mutation tool.

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 concise sentences. The first states the core function, and the second provides a practical example. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is adequate for a simple move operation but lacks details like specifying 'single thread' versus bulk, or behavior on existing data. It meets minimum viability but has room for improvement.

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 coverage is 100% with clear parameter descriptions. The tool description does not add extra meaning beyond the schema, so baseline score of 3 is appropriate.

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 action (move), the resource (email thread), and the destination (column or board). It distinguishes from sibling tools like 'move_card' by specifying 'email thread', but does not explicitly contrast with 'move_threads_bulk' for bulk operations.

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 provides usage context ('Use this to triage emails') and gives examples, but does not include when to avoid using it or mention alternative tools like 'move_threads_bulk' for batch moves.

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