Todoist AI MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

get-workspace-insights

Read-onlyIdempotent

Retrieve aggregated health and progress insights across all projects in a workspace. Optionally filter by project IDs to focus on specific projects for a cross-project health overview.

Instructions

Get aggregated health and progress insights across all projects in a workspace. Accepts workspace name or ID, with optional project ID filtering. Useful for a cross-project health overview.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`projectIds`	No	Optional list of project IDs to scope insights to specific projects.
`workspaceIdOrName`	Yes	The workspace ID or name. Supports exact ID, exact name match (case-insensitive), or unique partial name match.

Output Schema

TableJSON Schema

Name	Required	Description
`workspaceId`	Yes	The resolved workspace ID.
`workspaceName`	Yes	The resolved workspace name.
`projectInsights`	Yes	Health and progress insights for each project in the workspace.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv13.0.0Aug 20, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed15 schema fields changedv12.5.6Aug 12, 2026

removedOutput schema / properties / folderId

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "The folder ID, if applicable."
-}

addedOutput schema / properties / projectInsights / items / properties / health / additionalProperties
```
Added value: +false
```

removedOutput schema / properties / projectInsights / items / properties / health / anyOf

Removed value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "isStale": {
-        "description": "Whether the health data is stale.",
-        "type": "boolean"
-      },
-      "status": {
-        "description": "The health status of the project.",
-        "enum": [
-          "UNKNOWN",
-          "ON_TRACK",
-          "AT_RISK",
-          "CRITICAL",
-          "EXCELLENT",
-          "ERROR"
-        ],
-        "type": "string"
-      },
-      "updateInProgress": {
-        "description": "Whether a health analysis update is in progress.",
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "status",
-      "isStale",
-      "updateInProgress"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]

changedOutput schema / properties / projectInsights / items / properties / health / description

Previous value: -"Health data for this project, if available."New value: +"Health data for this project. Omitted when the project has none."

addedOutput schema / properties / projectInsights / items / properties / health / properties

Added value: +{
+  "isStale": {
+    "description": "Whether the health data is stale.",
+    "type": "boolean"
+  },
+  "status": {
+    "description": "The health status of the project.",
+    "enum": [
+      "UNKNOWN",
+      "ON_TRACK",
+      "AT_RISK",
+      "CRITICAL",
+      "EXCELLENT",
+      "ERROR"
+    ],
+    "type": "string"
+  },
+  "updateInProgress": {
+    "description": "Whether a health analysis update is in progress.",
+    "type": "boolean"
+  }
+}

addedOutput schema / properties / projectInsights / items / properties / health / required
```
Added value: +[
+  "status",
+  "isStale",
+  "updateInProgress"
+]
```
addedOutput schema / properties / projectInsights / items / properties / health / type
```
Added value: +"object"
```
addedOutput schema / properties / projectInsights / items / properties / progress / additionalProperties
```
Added value: +false
```

removedOutput schema / properties / projectInsights / items / properties / progress / anyOf

Removed value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "activeCount": {
-        "description": "Number of active tasks.",
-        "type": "number"
-      },
-      "completedCount": {
-        "description": "Number of completed tasks.",
-        "type": "number"
-      },
-      "progressPercent": {
-        "description": "Completion percentage (0-100).",
-        "type": "number"
-      }
-    },
-    "required": [
-      "completedCount",
-      "activeCount",
-      "progressPercent"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]

changedOutput schema / properties / projectInsights / items / properties / progress / description

Previous value: -"Progress data for this project, if available."New value: +"Progress data for this project. Omitted when the project has none."

addedOutput schema / properties / projectInsights / items / properties / progress / properties

Added value: +{
+  "activeCount": {
+    "description": "Number of active tasks.",
+    "type": "number"
+  },
+  "completedCount": {
+    "description": "Number of completed tasks.",
+    "type": "number"
+  },
+  "progressPercent": {
+    "description": "Completion percentage (0-100).",
+    "type": "number"
+  }
+}

addedOutput schema / properties / projectInsights / items / properties / progress / required
```
Added value: +[
+  "completedCount",
+  "activeCount",
+  "progressPercent"
+]
```
addedOutput schema / properties / projectInsights / items / properties / progress / type
```
Added value: +"object"
```

changedOutput schema / properties / projectInsights / items / required

Previous value: -[
-  "projectId",
-  "health",
-  "progress"
-]New value: +[
+  "projectId"
+]

changedOutput schema / required

Previous value: -[
-  "workspaceId",
-  "workspaceName",
-  "folderId",
-  "projectInsights"
-]New value: +[
+  "workspaceId",
+  "workspaceName",
+  "projectInsights"
+]

First observedv10.4.2Jul 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds context by noting the output is 'aggregated' and scoped 'across all projects', which goes beyond the schema and helps the agent understand the tool's behavior. No contradiction with 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?

The description is two sentences, front-loaded with the primary action and scope, then provides input details and a use case. Every sentence adds value and there is no wasteful repetition or filler.

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

Completeness5/5

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

For a simple read-only tool with a rich output schema, high schema parameter coverage, and strong annotations, the description fully covers purpose, input semantics, and usage context. No additional behavioral or output details are necessary, and the agent has enough information to select and invoke the tool.

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 only restates what the schema already says ('Accepts workspace name or ID, with optional project ID filtering') without adding additional format, defaults, or edge-case semantics, so it earns the baseline score.

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 a specific verb ('Get') and resource ('aggregated health and progress insights across all projects in a workspace'), which makes the core purpose unambiguous. It differentiates from project-specific tools by the 'across all projects' scope, though it does not explicitly name sibling alternatives or contrast with tools like get-productivity-stats.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'Useful for a cross-project health overview' provides a clear context for when to use this tool. However, it does not mention when not to use it or explicitly point to alternative sibling tools, so it stops short of a full 5.

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