linkding-mcp

Overview Schema Source Related Servers Discussions Admin

linkding_list_archived_bookmarks

Read-only

List archived bookmarks from Linkding using search, sorting, and filters for shared, unread, bundle, date, and pagination.

Instructions

List archived bookmarks. GET /api/bookmarks/archived/. Filters match linkding_list_bookmarks.

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": "linkding_list_archived_bookmarks"
  }
}

Input Schema

Name	Required	Description
`q`	No	Search phrase. Uses the same syntax as the Linkding UI.
`sort`	No	Sort order. Linkding defaults to added_desc.
`limit`	No	Page size. Linkding defaults to 100.
`bundle`	No	Bundle id. Only bookmarks matched by that bundle.
`offset`	No	Number of results to skip.
`shared`	No	Filter shared bookmarks. off, yes, or no.
`unread`	No	Filter unread bookmarks. off, yes, or no.
`added_since`	No	Only bookmarks added after this ISO 8601 timestamp.
`modified_since`	No	Only bookmarks modified after this ISO 8601 timestamp.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 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, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds only the archived-only scope and the underlying REST path; it says nothing about pagination behavior (limit/offset), default sort order, or what a result set looks like.

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?

Three short sentences with the archived scope front-loaded and no filler. The verbatim endpoint path is of marginal value to an agent but is compact and consistent with the rest of the server's descriptions.

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?

Nine optional parameters and no output schema mean the description should say a bit more about paging (limit/offset, default page size of 100) and result shape. The filter-parity pointer helps, but an agent must open the schema to learn the tool returns a limited page rather than all archived bookmarks.

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 coverage is 100% with per-parameter descriptions, enum values and defaults for all nine filters, so the description need not restate them. The single sentence 'Filters match linkding_list_bookmarks' is a useful pointer but adds no syntax or format detail beyond the schema; baseline 3 applies.

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 ('List archived bookmarks') and scopes it to the archived subset, which distinguishes it from linkding_list_bookmarks and linkding_list_shared_bookmarks. The explicit note that filters match linkding_list_bookmarks reinforces the distinction rather than repeating the name.

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?

Implicitly tells the agent to use this for archived items and that the filter semantics carry over from linkding_list_bookmarks, but never states when to prefer it over siblings like linkding_list_shared_bookmarks or how it relates to linkding_unarchive_bookmark. Usage is inferable rather than declared.

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