Skip to main content
Glama
Sign In
Commonpost MCP for Thunderbird

Commonpost MCP for Thunderbird

by commonpost
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Local

Create Task

createTask

Create a Thunderbird task with title, due date, priority, calendar, and categories; add it immediately or via the task dialog when settings require review.

Instructions

Create a task (to-do). No duplicate check: listTasks first. It is added at once (taskId in the result), unless the user's settings ask for Thunderbird's task dialog: then it exists once the user saves it (listTasks with the reviewId of the result tells).

Input Schema

NameRequiredDescriptionDefault
titleYesTask title
dueDateNoDue date in ISO 8601 format
priorityNoPriority: 1=high, 5=normal, 9=low
calendarIdNoTarget calendar ID (from listCalendars, must have supportsTasks=true)
categoriesNoCategory labels. Use listCategories to get exact existing names before setting.
skipReviewNotrue: add at once (refused if the settings ask for the dialog); false: open the dialog (default: the settings)
descriptionNoTask description/body

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / skipReview / description
      Previous value: -"Request direct saving without a review dialog. Honored only when the user explicitly disables the default-on skipReview safety block (default: false)."New value: +"true: add at once (refused if the settings ask for the dialog); false: open the dialog (default: the settings)"
  2. Changed4 schema fields changedv0.19.2
    • changedInput schema / properties / categories / description
      Previous value: -"Category labels (optional). Use listCategories to get exact existing names before setting."New value: +"Category labels. Use listCategories to get exact existing names before setting."
    • changedInput schema / properties / description / description
      Previous value: -"Task description/body (optional)"New value: +"Task description/body"
    • changedInput schema / properties / dueDate / description
      Previous value: -"Due date in ISO 8601 format (optional)"New value: +"Due date in ISO 8601 format"
    • changedInput schema / properties / priority / description
      Previous value: -"Priority: 1=high, 5=normal, 9=low (optional)"New value: +"Priority: 1=high, 5=normal, 9=low"
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, it discloses important behavior: no duplicate checking, immediate creation with a taskId, and an alternate path where the task exists only after the user saves it in Thunderbird's dialog. It even explains how to verify that path using listTasks and the reviewId, which is unusually transparent for a mutation tool.

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?

The description is short and front-loads the purpose and duplicate-check warning before explaining the conditional creation behavior. The final sentence is dense but every clause carries necessary behavioral information.

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 non-idempotent mutation with seven parameters and no output schema, the description covers the essential behavioral outcomes: immediate creation, dialog-based creation, duplicate-check absence, and result verification. Combined with the fully described schema, an agent has enough information to call and interpret the tool correctly.

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 schema already fully documents all seven parameters, including skipReview. The description adds some result semantics around taskId and reviewId but does not meaningfully deepen parameter interpretation beyond what the schema provides, so the 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 opens with a specific verb and resource, 'Create a task (to-do)', which unambiguously distinguishes it from sibling tools such as createEvent and updateTask. It also immediately adds scope by stating there is no duplicate check and that listTasks should be used first.

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?

It gives a clear pre-use step ('listTasks first') and explains the conditional outcome depending on user settings. It does not explicitly compare against createEvent or state when not to use this tool, but the task-vs-event distinction is strongly implied by the title and purpose.

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