Skip to main content
Glama
Sign In
linkwarden-mcp

linkwarden-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get a tag

get_tag
Read-only

Retrieve a specific tag's archival settings by its numeric ID, then use search_links with the tag ID to find associated links.

Instructions

Fetches one tag with its archival settings. Use search_links with tag_id to get the links carrying it.

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": {
      "tag_id": "<tag_id>"
    },
    "name": "get_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
tag_idYesNumeric id of the tag — the "id" field returned by list_tags

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.6/5.0
Behavior4/5

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

The description adds context beyond the readOnlyHint annotation by stating that it fetches 'archival settings' along with the tag, which hints at what the response includes. However, it does not disclose whether the tag is returned with its full metadata or any potential rate limits. The annotation already covers the safe read behavior, so the description provides useful additional detail.

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?

Two short sentences, zero waste. The first sentence states the core purpose, and the second provides a critical usage guideline. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the single required parameter, perfect schema coverage, readOnlyHint annotation, and no output schema, the description adequately covers the tool's purpose and how to use it. A small improvement would be to mention the response format or any pagination details, but it is largely complete for this simple tool.

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 coverage is 100% and the schema already describes tag_id well. The description adds value by mentioning 'archival settings' in the output, but does not elaborate on the parameter beyond what the schema provides. Since no further param info is needed, a 4 is justified.

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 'Fetches one tag with its archival settings', which is a specific verb + resource combination. It also distinguishes from sibling tools like search_links, get_link, and list_tags by specifying what it does (fetches a tag with archival settings) and what it doesn't do (get links).

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?

The description explicitly tells when to use this tool and when not to: it says to use search_links with tag_id to get the links carrying the tag. This provides clear guidance on using an alternative sibling tool for related functionality, making the decision boundary unambiguous.

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