Skip to main content
Glama
Sign In
Google Tasks MCP Server

Google Tasks MCP Server

by odise444
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Google Tasks 목록 조회

tasks_list
Read-onlyIdempotent

List all Google Tasks, including completed and pending items, with details like due dates and notes. Filter by status to view only pending or completed tasks.

Instructions

Google Tasks의 모든 할 일을 조회합니다.

완료된 항목과 미완료 항목을 모두 반환합니다. 각 항목에는 id, 제목, 상태, 마감일, 메모, 목록 이름이 포함됩니다.

Returns:

  • tasks: 할 일 배열 (id, title, status, due, notes, listTitle)

  • total: 전체 개수

  • pending: 미완료 개수

Examples:

  • "할 일 목록 보여줘" -> tasks_list()

  • "Tasks 전체 조회" -> tasks_list()

  • "완료 안 된 것만 보여줘" -> tasks_list() 후 status 필터링

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": "tasks_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNo조회 필터: all=전체, pending=미완료만, completed=완료만all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description adds valuable context: it returns both completed and uncompleted items, and includes counts (total, pending). This gives the agent a clear expectation of the response structure.

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 reasonably concise, front-loaded with the main purpose, and well-structured with Returns and Examples sections. The examples are useful, though the misguidance about filtering adds some noise.

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 simple list tool, the description covers the return fields and gives examples. However, the complete omission of the filter parameter from the description creates a significant information gap, even though the schema documents it. Without mentioning filtering, the agent may not know the tool can filter directly.

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

Parameters2/5

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

Schema coverage is 100%, but the description does not mention the filter parameter at all. Worse, the example '완료 안 된 것만 보여줘' suggests calling tasks_list() with no arguments and filtering afterwards, which contradicts the schema's filter capability. This is misleading and fails to add meaning beyond the schema.

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 'Google Tasks의 모든 할 일을 조회합니다' (retrieves all Google Tasks), specifying the exact verb and resource. It clearly differentiates from sibling mutation tools (add, complete, delete, update) by focusing on retrieval.

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?

Provides concrete examples mapping user intents like '할 일 목록 보여줘' to tasks_list(), which is good practical guidance. However, it doesn't explicitly state when to use this over alternatives, though the read-only nature and examples make it clear enough.

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