google-keep-mcp

create_note

Create a new text note in Google Keep. Set title, body, color, pin status, and labels to organize your notes.

Instructions

Create a new text note in Google Keep.

Args: title: Note title. text: Note body text. color: Note color (e.g. "yellow", "blue", "green"). pinned: Whether to pin the note. labels: Label names to apply (created if they don't exist).

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

Input Schema

Name	Required	Description	Default
`text`	No
`color`	No
`title`	No
`labels`	No
`pinned`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 16, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It mentions labels are created if they don't exist, but does not disclose other behaviors like default values, immediate availability, or auth requirements. Adequate but not comprehensive.

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?

Single sentence with a list of parameters. No superfluous information. Front-loaded purpose.

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 5 optional parameters and an output schema, the description covers all inputs and the core action. No missing context for a create tool.

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

Parameters5/5

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

Schema has 0% coverage, but description provides a clear one-liner for each parameter (title, text, color with examples, pinned boolean, labels with note about creation). Fully compensates for schema deficiency.

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 'Create a new text note in Google Keep' with a specific verb and resource. Among sibling tools like 'update_note' and 'trash_note', this is distinct and unambiguous.

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?

No explicit guidance on when to use this tool versus alternatives like 'bulk_update_notes' or 'create_list'. Usage is inferrable from the action, but lacking proactive context.

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

Deploy Server