driftnet

Search the catalogue

driftnet_search_items

Read-onlyIdempotent

Search the reader’s catalogue of AI tools, repos, videos, and guides shared in chats before choosing a tool; filter by query, folder, kind, date, or rating to find vetted items.

Instructions

Find items in the reader's catalogue of AI tools, repos, videos and guides that people shared in chats. Call it before choosing a tool for a task, since someone may already have vetted one; once you have an id and need the whole card, use driftnet_get_item instead. query is matched word by word (every word must appear) against names, summaries, tags, URLs, folder names, the reader's notes and the chat text a link was shared with, so 'pdf markdown' finds 'Convert PDF to Markdown' (it also matches by meaning when the reader turned that on); omit it to browse. If nothing matches, misspelt words are corrected and corrected says what was searched instead. days switches the order to newest first, which is how to ask what's new. view=trash is how to find an id to restore with driftnet_update_item; view=inbox adds each item's suggested folders. folder also covers its sub-folders. Dead, archived or stale links are marked in health. Results come best first (must-see, then newest) and never include down-voted or prompt-injection-flagged items. There is no paging: when limit cuts results off, narrow with query, folder, kind or days.

Input Schema

Name	Required	Description
`days`	No	Only items added in the last N days, 1–90, newest first; omit for any time
`kind`	No	Only this kind of link, e.g. 'repo'; omit for all kinds
`view`	No	all (default), inbox, favorites, trash, or needs_review (dead, archived or stale links)
`limit`	No	Maximum items, 1–50; default 10
`query`	No	Free text, 1–200 chars, e.g. 'pdf to markdown' or a tool name; omit to list without filtering
`folder`	No	Folder id from driftnet_list_folders, e.g. 'coding'; includes its sub-folders. Omit for every folder
`min_worth`	No	Rating floor, skip < low < normal < must-see; default 'normal'

Output Schema

Name	Required	Description	Default
`items`	Yes
`notice`	Yes
`corrected`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.0Oct 30, 2026
- addedOutput schema / properties / corrected
```
Added value: +{
+  "type": "string"
+}
```

Changed5 schema fields changedv0.8.0Oct 29, 2026

changedInput schema / properties / view / description

Previous value: -"all (default), inbox, favorites or trash"New value: +"all (default), inbox, favorites, trash, or needs_review (dead, archived or stale links)"

changedInput schema / properties / view / enum

Previous value: -[
-  "all",
-  "inbox",
-  "favorites",
-  "trash"
-]New value: +[
+  "all",
+  "inbox",
+  "favorites",
+  "trash",
+  "needs_review"
+]

addedOutput schema / properties / items / items / properties / health
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / items / items / properties / stars
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```

changedOutput schema / properties / items / items / required

Previous value: -[
-  "id",
-  "name",
-  "url",
-  "category",
-  "kind",
-  "worth",
-  "one_liner",
-  "demo",
-  "why",
-  "highlights",
-  "tags",
-  "shared",
-  "added",
-  "page_url",
-  "in_inbox",
-  "suggested_folders"
-]New value: +[
+  "id",
+  "name",
+  "url",
+  "category",
+  "kind",
+  "worth",
+  "one_liner",
+  "demo",
+  "why",
+  "highlights",
+  "tags",
+  "shared",
+  "added",
+  "page_url",
+  "in_inbox",
+  "health",
+  "stars",
+  "suggested_folders"
+]

Addedv0.7.0Oct 29, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already declare this as a read-only, idempotent, non-destructive search, but the description adds substantial behavioral detail beyond them. It explains word-by-word matching, optional semantic matching, misspelling correction, ordering, exclusions, health marking, and absence of paging.

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?

The description is dense but front-loaded, opening with the core action and the most important sibling-routing rule. Every sentence carries operational value for a seven-parameter search tool, and there is no filler.

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 annotations covering safety, a full schema with descriptions, and an output schema, the description still supplies the non-obvious matching, ordering, exclusion, and paging behavior an agent needs. It is complete for correct selection and invocation.

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?

Although schema coverage is 100%, the description adds meaningful semantics beyond the schema for multiple parameters. It explains how query matches across fields, how days changes ordering, how view=trash and view=inbox are used, how folder includes sub-folders, and how limit interacts with paging.

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 states a specific verb and resource: finding items in the reader's catalogue of AI tools, repos, videos, and guides shared in chats. It clearly distinguishes the search operation from driftnet_get_item, which is named as the follow-up for retrieving a full card by id.

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

Usage Guidelines5/5

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

It explicitly says to call this before choosing a tool for a task and names driftnet_get_item as the alternative once an id is known. It also gives concrete routing guidance for trash and restore flows, inbox suggestions, no-paging behavior, and how to narrow when limit cuts results off.

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

Deploy Server