Skip to main content
Glama

Search and list links

search_links
Read-only

Find and filter bookmarks by title, URL, description, or tag. Lists all links when no query is given, with pagination and optional filters by collection or tag.

Instructions

Searches bookmarks, or lists them when no query is given. This is the way to find links — there is no separate list tool, and the older /links listing route is deprecated upstream.

Plain text matches the title, URL, description and tag names of a link.

IMPORTANT: the field-filter syntax below only works on instances that run Meilisearch. Linkwarden parses those filters exclusively in its Meilisearch branch; without it the whole query is matched as one literal substring, so tag:news searches for the characters "tag:news" and finds nothing. Use the collection_id, tag_id and pinned_only arguments instead — those are applied by the database and work either way. list_collections and list_tags give you the ids.

Where Meilisearch is available the filters are: url: name: description: type: collection: tag: pinned: public: before: after: Quote values that contain spaces, e.g. collection:"Read later". Prefix a filter with ! to negate it, e.g. !tag:archive. pinned: and public: take true or false; before: and after: take a date such as 2026-01-31. If the instance sets SEARCH_FILTER_LIMIT, field filters beyond that count are dropped silently, so prefer few, specific filters.

Returns at most 100 links plus a next_cursor for the following page. Article text is not included; use get_link_content for that.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order, default date_newest
queryNoSearch query, see the syntax above. Omit to list links.
cursorNoOpaque pagination cursor. Pass back the "next_cursor" value from a previous result verbatim; do not compute or increment it — depending on whether the instance runs Meilisearch it is either a row offset or the last id seen.
tag_idNoRestrict the result to this tag
pinned_onlyNoOnly return links pinned by the authenticated account
collection_idNoRestrict the result to this collection
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds behavioral details: returns at most 100 links, pagination via cursor, article text not included (referencing get_link_content), and the silent dropping of filters when SEARCH_FILTER_LIMIT is exceeded. This adds value beyond the annotations.

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?

The description is fairly long but front-loaded with the main purpose. The detailed filter syntax and pagination notes are necessary for correct usage. It could be slightly more concise, but it is well-structured with clear sections.

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?

Given the complexity (6 parameters, no output schema), the description is complete. It explains the query syntax, pagination mechanism, limitations (Meilisearch dependency, filter count limit), and what is not included (article text). It also references related tools for IDs and content.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already documents each parameter. The description adds significant context for the query parameter (Meilisearch filter syntax, quoting, negation, date format) and for cursor (opaque, do not compute or increment). This adds meaning beyond the schema.

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 'Searches bookmarks, or lists them when no query is given,' which is a specific verb+resource. It also distinguishes from siblings by noting there is no separate list tool and that the older /links route is deprecated.

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

Usage Guidelines4/5

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

The description provides extensive guidance on when to use the field-filter syntax vs. the structured arguments, and explicitly warns about the Meilisearch dependency. It suggests using list_collections and list_tags to get IDs. It does not explicitly state when not to use this tool, but the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ni-c/linkwarden-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server