Skip to main content
Glama
Sign In

Milanote MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Set due date

set_due_date
Destructive

Set, change or remove the due date of one task in a to-do list. Finds the task by task_id or by its exact text and sets its due date, or removes it when due_date is null. A date without a time is due at 5 PM; Milanote reminds you at 9 AM the day it's due. Times are in the Cloud Browser's time zone. The task's text and done state stay as they were. Returns the whole list after the change. When two tasks share the text, pass the task_id instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "board_id": "<board_id>",
      "card_id": "<card_id>",
      "task": "<task>",
      "due_date": "<due_date>"
    },
    "name": "set_due_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesThe task's task_id from get_board, or its exact text.
card_idYesTo-do list ID from get_board.
board_idYesBoard ID from list_boards, or the board URL.
due_dateYesYYYY-MM-DD. null or an empty string removes the due date.
due_timeNoHH:MM, 24-hour, with due_date. Default: no time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, it discloses the 5 PM default due time, 9 AM reminder behavior, timezone handling, that text and done state are preserved, and that the whole list is returned. It also makes the destructive removal behavior explicit via due_date null.

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 dense but front-loaded, with no wasted sentences. Each clause contributes either selection guidance, behavioral context, or parameter meaning.

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?

With no output schema, the description states what is returned: the whole list after the change. It covers the mutation semantics, default times, timezone, and task disambiguation needed to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3. The description still adds meaningful semantics: task may be an ID or exact text, duplicate text requires task_id, and date-only values default to 5 PM while due_time can override that.

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 states a specific verb and resource: setting, changing, or removing the due date of one task in a to-do list. It is clearly distinct from sibling tools like set_task_done and add_task.

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 explains how to identify the target task by task_id or exact text and explicitly says to use task_id when texts are duplicated. It does not compare against alternative tools, but the usage context for this tool itself is clear.

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

All Milanote MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources