DragApp MCP Server

toggle_labels

Add or remove multiple labels on a thread in one call, streamlining label management and reducing API requests.

Instructions

Add some labels and/or remove others from a thread in one call. The backend toggle endpoint is one-label-at-a-time, so this iterates internally.

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>",
      "boardId": "<boardId>"
    },
    "name": "toggle_labels"
  }
}

Input Schema

Name	Required	Description
`boardId`	Yes	The board ID the thread belongs to
`threadId`	Yes	The thread or task ID
`addLabelIds`	No	Label IDs to add
`removeLabelIds`	No	Label IDs to remove

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.5Jul 7, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The description reveals that the backend operates one-label-at-a-time and the tool handles iteration internally, a behavioral trait beyond the schema and annotations.

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 sentences with no waste: states purpose and internal behavior efficiently.

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

Completeness4/5

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

Given no output schema or annotations, the description adequately covers purpose and behavior, though it omits error handling or return details.

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

Parameters4/5

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

Schema coverage is 100%, and the description adds context by explaining the batch operation, though the parameters themselves are well described in the schema.

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 adds and/or removes labels from a thread, distinguishing it from sibling tools like add_label_to_thread and remove_label_from_thread by enabling both actions in one call.

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 for batch operations but lacks explicit guidance on when to use this tool versus the single-label siblings. The note about internal iteration offers minimal context.

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