FeedKeeper Cloud

Search articles by keyword or phrase

search_items

Read-onlyIdempotent

Searches article titles and summaries using SQLite FTS5 full-text search across all accessible items. Returns matching articles matching the query phrase, with optional feed, folder, bookmark, and date filters. Safe read-only search.

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": {
      "query": "<query>"
    },
    "name": "search_items"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of search results to return (1 to 200, default: 50)
`query`	Yes	The search term or phrase to find in article titles and content summaries
`since`	No	Filter for items published at or after this ISO date or date-time
`until`	No	Filter for items published at or before this ISO date or date-time
`feedId`	No	Optional feed ID filter
`folderId`	No	Optional folder ID filter
`bookmarkedOnly`	No	When true, restricts search to bookmarked items

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the closing 'Safe read-only search' sentence mostly restates structured data. The description does add real context by disclosing the FTS5 backend and that matching happens against titles and summaries across all accessible items, but it omits result ordering, relevance ranking, and pagination behavior.

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?

Two front-loaded sentences with the core purpose first and filters second; minimal waste. The second sentence is slightly redundant in phrasing ('Returns matching articles matching the query phrase'), which keeps it from a 5.

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?

With seven parameters, full schema coverage, and no output schema, the description covers scope and filters adequately, but leaves unanswered how query strings are parsed and how results are ordered or truncated. For a search tool whose main risk is misusing the query syntax, that is a meaningful gap.

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, and the description's mention of feed, folder, bookmark, and date filters adds no syntax or semantics beyond the schema. It also does not explain how FTS5 interprets the query string (phrase vs. term matching, operators), which is the one piece of meaning the schema cannot convey.

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 and resource ('Searches article titles and summaries') plus the underlying mechanism (SQLite FTS5) and scope ('all accessible items'). It is clearly a keyword search rather than a listing, though it never names the sibling list_items or get_new_items it contrasts with, so differentiation is left partly to inference.

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?

Usage is only implied: the presence of optional feed/folder/bookmark/date filters suggests narrowing a text query, but there is no explicit guidance on when to search versus browsing via list_items, get_new_items, or get_digest. No exclusions or prerequisites are stated.

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

All FeedKeeper Cloud tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?