Skip to main content
Glama
greirson

Todoist MCP Server

todoist_activity_get

Retrieve Todoist activity logs with optional filters to audit changes, track productivity, and review workspace history.

Instructions

Get Todoist activity log with optional filters. Returns events for items, notes, projects, sections, labels, filters, and reminders. Useful for auditing changes, tracking productivity, and understanding workspace history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_typeNoFilter by object type: 'item' (tasks), 'note' (comments), 'project', 'section', 'label', 'filter', or 'reminder'
object_idNoFilter by specific object ID
event_typeNoFilter by event type: 'added', 'updated', 'deleted', 'completed', 'uncompleted', 'archived', 'unarchived', 'shared', or 'left'
parent_project_idNoFilter by parent project ID
parent_item_idNoFilter by parent item/task ID (for subtask events)
initiator_idNoFilter by user ID who initiated the action
sinceNoReturn events after this date/time (ISO 8601 format, e.g., 2024-01-01T00:00:00Z)
untilNoReturn events before this date/time (ISO 8601 format, e.g., 2024-12-31T23:59:59Z)
limitNoMaximum number of events to return (default: 30, max: 100)
offsetNoNumber of events to skip for pagination
Behavior2/5

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

No annotations provided, so description carries full burden. It does not declare if the operation is read-only, requires authentication, or has side effects. Merely states it returns events, lacking disclosure of safety implications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, concise and front-loaded. The second sentence lists use cases but could be more specific. Efficient overall, though slightly generic.

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?

Lacks return format details, sorting, default pagination (limit 30). No differentiation from sibling activity tools. Incomplete for a tool with no output schema and multiple related siblings.

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?

Input schema has 100% coverage with descriptions, so the description adds little extra value. It lists object types but does not explain parameters beyond schema. Baseline 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?

Description clearly states it retrieves activity logs with optional filters and lists object types. Suggests use cases like auditing and tracking productivity. However, it does not explicitly differentiate from sibling tools such as todoist_activity_by_date_range.

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?

Description mentions usefulness for auditing and tracking but fails to provide guidance on when to use this tool versus other activity tools. No when-not-to-use or alternative suggestions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/greirson/mcp-todoist'

If you have feedback or need assistance with the MCP directory API, please join our Discord server