Skip to main content
Glama
Karakeep MCP server

Karakeep MCP server

by karakeep-app

create-list

Create a named bookmark list with an emoji icon and optional parent list to organize saved bookmarks into structured collections.

Instructions

Create a list.

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": {
      "name": "<name>",
      "icon": "<icon>"
    },
    "name": "create-list"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconYesThe emoji icon of the list.
nameYesThe name of the list.
parentIdNoThe parent list id of this list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.35.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observed

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about permissions, duplicate-name handling, or what happens when parentId is omitted. The only information conveyed is that the operation is a creation, which is the bare minimum.

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

Conciseness2/5

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

The single four-word sentence contains no waste but is under-specified rather than concise; it fails to front-load any useful constraint or context. Brevity here costs the agent information rather than saving it.

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

Completeness2/5

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

For a mutation tool with a parentId parameter implying a list hierarchy, no annotations, and no output schema, the description should explain nesting semantics and what is returned. It leaves the agent to guess how parentId behaves and whether the new list is a root list by default.

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% description coverage for all three parameters (name, icon, parentId), so the schema documents them adequately. The description adds nothing beyond that, which meets the baseline of 3 when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description reads "Create a list." which is essentially the tool name restated with a verb. It does not distinguish the tool from siblings such as create-bookmark or add-bookmark-to-list, nor does it say what a "list" is in this domain.

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?

There is no guidance on when to use this tool, no preconditions, and no mention of related operations like add-bookmark-to-list (which requires a list to exist first). The agent must infer the whole workflow from the sibling names.

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