Skip to main content
Glama
si-essence

wallabag

by si-essence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

wallabag_entries

Destructive

Manage saved articles, tags, and metadata in a self-hosted read-later service. Run get, post, patch, or delete operations with dry-run previews and explicit confirmation before writes.

Instructions

wallabag_entries covers the entries toolset (14 operations). Auth is OAuth2 Bearer from WALLABAG_ACCESS_TOKEN or a password grant. Self-hosted Wallabag first. action help with target returns one action's parameters. Writes need confirm set to the boolean true and WALLABAG_ALLOW_WRITES=true. Omit confirm for a dry-run preview that sends nothing. Destructive actions add an extra warning in the preview: deletes, bulk URL lists, and user registration. Actions: delete_by_id, delete_list, delete_tags, delete_tags_list, get, get_by_id, get_exists, get_tags, patch_by_id, patch_reload, post, post_lists, post_tags, post_tags_lists.

Input Schema

NameRequiredDescriptionDefault
bodyNoJSON body for the Wallabag operation. Secrets are redacted in output.
queryNoQuery parameters.
actionYesWallabag operation to call, or help.
paramsNoExpress path parameters, such as id.
targetNoWith action help, the action whose parameters to describe.
confirmNoSet to the boolean true to execute the write. Omit this field for a dry-run preview. false and the string true are rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Beyond annotations, the description discloses OAuth2 auth sources, the write-gating environment variable, dry-run behavior that sends nothing, and the extra destructive warning shown for deletes, bulk URL lists, and user registration. These details substantially improve safe invocation and do not contradict 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 front-loaded and information-dense, with auth and write safety before the action list. The long action enumeration duplicates the schema enum and makes the paragraph run-on, but it is not padded with fluff.

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?

For a complex 14-operation tool with six parameters, the description covers auth, write safety, dry-run behavior, and how to discover per-action parameters via help. It does not explain return values or per-action semantics, but the help action mitigates the biggest invocation 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 the schema already carries most parameter meaning. The description reinforces action help, target, and confirm semantics, but it largely repeats what the schema states and does not add new syntax or format guidance for body, query, or params.

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?

The description states that the tool covers the Wallabag entries toolset and enumerates all 14 supported actions, giving a clear verb/resource picture. It does not explicitly distinguish the tool from siblings such as wallabag_search, so it falls short of a 5.

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?

It gives clear operational guidance: use action help with target to inspect parameters, writes require confirm=true plus WALLABAG_ALLOW_WRITES=true, and omitting confirm produces a dry-run preview. It does not say when to choose this tool over sibling tools like wallabag_search, but the usage context is otherwise strong.

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