Skip to main content
Glama
Doist

Todoist AI MCP Server

Official
by Doist
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-project-activity-stats

Read-onlyIdempotent

Retrieve daily and weekly task completion counts for a project across 1-12 weeks to identify activity trends and patterns.

Instructions

Get daily and optional weekly task completion counts for a project over a configurable time window (1-12 weeks). Useful for identifying completion trends and patterns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
weeksNoNumber of weeks of activity data to retrieve (1-12, default 2).
projectIdYesThe ID of the project to get activity stats for.
includeWeeklyCountsNoInclude weekly rollup counts alongside daily counts.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayItemsYesDaily task completion counts.
projectIdYesThe project ID.
weekItemsNoWeekly completion rollups. Only included when includeWeeklyCounts is true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv13.0.0
    • 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"
  2. Changed4 schema fields changedv12.5.6
    • removedOutput schema / properties / weekItems / anyOf
      Removed value: -[
-  {
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "fromDate": {
-          "description": "Start date of the week.",
-          "type": "string"
-        },
-        "toDate": {
-          "description": "End date of the week.",
-          "type": "string"
-        },
-        "totalCount": {
-          "description": "Number of tasks completed in this week.",
-          "type": "number"
-        }
-      },
-      "required": [
-        "fromDate",
-        "toDate",
-        "totalCount"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / weekItems / items
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "fromDate": {
+      "description": "Start date of the week.",
+      "type": "string"
+    },
+    "toDate": {
+      "description": "End date of the week.",
+      "type": "string"
+    },
+    "totalCount": {
+      "description": "Number of tasks completed in this week.",
+      "type": "number"
+    }
+  },
+  "required": [
+    "fromDate",
+    "toDate",
+    "totalCount"
+  ],
+  "type": "object"
+}
    • addedOutput schema / properties / weekItems / type
      Added value: +"array"
    • changedOutput schema / required
      Previous value: -[
-  "projectId",
-  "dayItems",
-  "weekItems"
-]New value: +[
+  "projectId",
+  "dayItems"
+]
  3. First observedv10.4.2

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds context about granularity and time window but does not disclose additional behavioral aspects like handling of missing data or aggregation details. This is adequate given the annotation coverage.

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, directly states the function, and includes a usage note. No filler or redundancy, earning a perfect score for conciseness.

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 statistics tool with an output schema, the description covers the essential purpose, scope, and use case. It does not need to explain return format since the output schema exists, and annotations cover safety. It is complete for the tool's complexity.

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%, so all parameters are documented in the schema. The description adds contextual meaning (e.g., 'daily' and 'weekly' align with weeks and includeWeeklyCounts) but does not deeply explain parameter semantics beyond the schema. Baseline of 3 is appropriate.

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 verb 'Get' and resource 'project activity stats' (task completion counts), with scoping details (daily, optional weekly, time window). It distinguishes from siblings like get-productivity-stats and find-activity by focusing on project-specific completion trends.

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 description provides a clear use case ('identifying completion trends and patterns'), which implies when to use it. However, it does not explicitly mention alternatives or when not to use it, so it lacks exclusions.

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

Deploy Server

Other Tools