google-keep-mcp

create_note

Create a new note in Google Keep with an optional title and text. Store and organize your ideas directly in your Keep account.

Instructions

Create a new note with title and text.

Args:
    title (str, optional): The title of the note
    text (str, optional): The content of the note
    
Returns:
    str: JSON string containing the created note's data

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
`title`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Jul 13, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries full behavioral disclosure burden. It only mentions the return type (JSON string) but omits side effects, required permissions, error conditions, or constraints like uniqueness of title.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and includes Args/Returns sections, making it structured. However, the Args section is redundant with the schema, and the Returns section is basic.

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?

Given the low complexity (2 optional params, output schema exists), the description covers the basic purpose and return type. However, it lacks details such as what happens when parameters are omitted, validation rules, or error handling.

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

Parameters1/5

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

Schema description coverage is 0% and the description merely restates the parameter names and types already in the schema (str, optional). No additional meaning is provided beyond what the structured data offers.

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 tool creates a new note with title and text, using a specific verb and resource. It distinguishes from sibling operations like archive_note, delete_note, etc., which have different purposes.

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

Usage Guidelines2/5

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

The description lacks guidance on when to use this tool versus alternatives. No context is given about prerequisites, limitations, or when other sibling tools would be more appropriate.

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

Deploy Server