Dotloop MCP

dotloop_get_task_list

Fetch a specific task list from a Dotloop loop using profile, loop, and tasklist IDs.

Instructions

Get one Dotloop task list.

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": {
      "profile_id": "<profile_id>",
      "loop_id": "<loop_id>",
      "tasklist_id": "<tasklist_id>"
    },
    "name": "dotloop_get_task_list"
  }
}

Input Schema

Name	Required	Description	Default
`loop_id`	Yes
`profile_id`	Yes
`tasklist_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 27, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations, the description should disclose behavioral traits (e.g., read-only, return format). It only states the action without mentioning what the response contains or any side effects, limiting transparency.

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 very short and to the point, but it lacks any structure beyond a single sentence. While concise, it does not provide enough substance to be considered highly effective.

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 presence of an output schema, the description is partially adequate, but it omits any mention of the output or contextual details about when to use this tool. It feels insufficient for a complete understanding.

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

Parameters1/5

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

The input schema has 0% description coverage, and the description adds no information about parameter semantics. Parameter names like 'profile_id', 'loop_id', and 'tasklist_id' are somewhat self-explanatory, but the tool description provides no additional context or usage hints.

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 retrieves a single task list. It uses a specific verb ('Get') and resource ('task list'), distinguishing it from sibling tools like 'dotloop_list_task_lists' which retrieves multiple lists.

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 like 'dotloop_list_task_lists' or 'dotloop_get_task'. The description lacks context for decision-making.

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

Deploy Server