Skip to main content
Glama
Sign In
google-tasks-mcp-server

google-tasks-mcp-server

by Kouta-i5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

タスク作成

create-task

Create a new Google Task with title, optional due date, notes, parent for subtasks, and position. Add tasks directly to a specific task list.

Instructions

タスクを作成する。parent を指定するとサブタスクになる。

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": {
      "title": "<title>"
    },
    "name": "create-task"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueNo期限。RFC 3339 形式（例: 2026-08-30T00:00:00.000Z）。Google Tasks は日付部分のみ保持し、時刻は無視される。
notesNoメモ・詳細
titleYesタスクのタイトル
parentNo親タスクの ID。指定するとサブタスクとして作成する。
previousNo直前に置くタスクの ID。省略するとリストの先頭に入る。
tasklistNoタスクリストの ID。既定のリストは '@default'。ID は list-tasklists で取得できる。@default

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that specifying 'parent' creates a subtask, but this behavior is already documented in the input schema. It does not disclose other relevant traits such as the write nature of the operation, potential side effects, or default tasklist behavior beyond the schema. The description adds minimal value beyond what the schema already states.

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 a single sentence that front-loads the core action and immediate behavioral nuance. There is no fluff, repetition, or unnecessary elaboration, making it highly efficient for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 6 parameters and no annotations or output schema, the description is minimal but not critically insufficient. It states the core function and subtask behavior, while relying on the schema for parameter details. However, it does not provide broader workflow guidance (e.g., how to obtain a tasklist ID) or clarify return behavior, leaving some gaps for an agent evaluating usage context.

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?

The input schema has 100% parameter description coverage, so the baseline is 3. The description only references 'parent' indirectly and adds no semantic detail beyond the schema's own parameter descriptions. It does not clarify relationships between parameters or provide examples, but the schema already handles this adequately.

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 action ('タスクを作成する' - create a task) and identifies the key distinction that specifying 'parent' makes it a subtask. This unambiguously separates it from sibling tools like create-tasklist, which creates a task list instead.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for creating a task but does not explicitly contrast with alternatives or provide when-not-to-use guidance. No exclusions, prerequisites, or references to related tools (e.g., list-tasklists) are given, so the usage context is only inferred from the 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