Skip to main content
Glama
Sign In
Todoist MCP Server

Todoist MCP Server

by greirson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

todoist_section_archive

Archive a section in Todoist to hide it and its tasks without deletion.

Instructions

Archive a section. Archived sections are hidden but not deleted. Tasks in the section are also archived.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "todoist_section_archive"
  }
}

Input Schema

NameRequiredDescriptionDefault
section_idNoThe ID of the section to archive
section_nameNoThe name of the section to archive (partial match, case-insensitive)
project_idNoOptional project ID to narrow section search

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.3

TDQS

A3.8/5.0
Behavior4/5

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

Discloses that archived sections are hidden but not deleted and tasks within are also archived. This adds value beyond the input schema, but does not mention reversibility or any restrictions (e.g., cannot archive sections with uncompleted tasks).

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 concise sentences that deliver key information without fluff. Every sentence is informative and earns its place.

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?

Covers the essential behavioral outcomes (hidden/not deleted, tasks archived) for a simple archive action. Lacks return value info and error cases, but these are often implicit for such operations. Sufficient for the tool's simplicity.

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% description coverage for parameters. The description does not add extra meaning beyond the schema, such as precedence when both section_id and section_name are provided. Baseline 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 tool archives a section, distinguishes it from deletion (hidden but not deleted) and mentions tasks are also archived, effectively differentiating it from siblings like todoist_section_delete and todoist_section_unarchive.

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 on when to use archiving vs deletion or unarchiving, nor any prerequisites (e.g., section must exist, user permissions). Context for appropriate usage is missing.

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