Skip to main content
Glama
Sign In
Keep It MCP Server

Keep It MCP Server

by sglewis100
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

keepit_search_items

Search Keep It items by text query, folder, bundle, tag, or favorite status to locate notes and documents in your library.

Instructions

Search items in Keep It by text query, folder, bundle, tag, or favorite 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": "keepit_search_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoFilter items tagged with this tag
limitNoMaximum items to return
queryNoSearch text matching name, comments, or tags
bundleNoFilter items within this bundle name
folderNoFilter items within this folder name
is_favoriteNoFilter only favorite items

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing beyond the facet list. It does not say whether multiple filters are ANDed or ORed, how results are ordered, how the default limit of 50 behaves, or whether the operation is paginated — all relevant for a search tool with six optional parameters.

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?

A single front-loaded sentence with no wasted words, and the resource is named before the facet list. It is efficient, though it is essentially a compressed restatement of the parameter set rather than added information.

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 six-parameter search tool with no annotations and no output schema, the description is thin: it omits filter combination semantics, result ordering, and limit/default behavior. An agent could call it, but not confidently predict what the results or filter interactions will be.

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?

Schema description coverage is 100%, so every parameter is already documented in the schema and the baseline is 3. The description's mention of query/folder/bundle/tag/favorite simply restates those same parameters without adding syntax, matching behavior, or interaction rules.

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

Purpose4/5

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

States a specific verb (search) and resource (items in Keep It) plus the available facets, so the agent knows this is a read-only query tool rather than a mutation or single-item fetch. It does not explicitly differentiate itself from siblings like keepit_get_item or keepit_get_selected_items, which is why it stops short of a 5.

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 statement of when to use this tool versus keepit_get_item, keepit_get_current_item, or keepit_get_selected_items, nor any exclusion or prerequisite guidance. The only implied usage comes from the word 'search' itself.

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