Skip to main content
Glama
bezata

kObsidian MCP

by bezata

Modify Tags

tags.modify
Idempotent

Update a note's frontmatter tags by adding, removing, or replacing them. Manage tag lists idempotently, with automatic # stripping, leaving inline tags untouched.

Instructions

Mutate the frontmatter tags list of a single note. Four ops are supported: add unions the incoming tags with the existing list (duplicates dropped); remove drops any incoming tag currently present; replace overwrites the list entirely; merge is an alias for add. Leading # on incoming tags is stripped automatically. This tool only touches the frontmatter block — inline #tag occurrences in the body are left untouched. Idempotent: repeated calls with the same op and tags converge on the same result. Returns {changed, target, summary, op, tagsAfter}.

Operates on the session-active vault (see vault.current — selectable via vault.select) unless an explicit vaultPath argument is passed, which always wins.

Examples:

Example 1 — Add two tags to a note (idempotent):

{
  "path": "Projects/Alpha.md",
  "op": "add",
  "tags": [
    "in-progress",
    "priority/high"
  ]
}

Example 2 — Replace a note's entire tag set:

{
  "path": "Inbox/today.md",
  "op": "replace",
  "tags": [
    "processed"
  ]
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opYesThe mutation to apply to the note's frontmatter `tags` field: - `add` — union existing + incoming (duplicates dropped). - `remove` — drop any incoming tag that currently exists. - `replace` — overwrite the tag list entirely with `tags`. - `merge` — alias for `add` (kept for naming clarity; behaves identically).
pathYesVault-relative note path to mutate.
tagsYesTags to add/remove/replace with. Leading `#` is stripped automatically. Max 50 per call.
vaultPathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
opYesThe mutation to apply to the note's frontmatter `tags` field: - `add` — union existing + incoming (duplicates dropped). - `remove` — drop any incoming tag that currently exists. - `replace` — overwrite the tag list entirely with `tags`. - `merge` — alias for `add` (kept for naming clarity; behaves identically).
targetYes
changedYes
summaryYes
tagsAfterYesThe full tag list after the mutation.
tagsBeforeNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv0.3.5
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Addedv0.1.2

TDQS

A4.7/5.0
Behavior5/5

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

The description goes well beyond the annotations: it confirms and elaborates idempotency ('repeated calls with the same op and tags converge'), discloses that leading '#' is stripped, specifies that only the frontmatter block is modified (leaving inline tags untouched), and details the exact behavior of each operation. It also states the return object format. All of this adds behavioral context that annotations alone do not provide.

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 well-structured and front-loaded with the core purpose, followed by operation semantics, vault behavior, and concrete examples. It is detailed but every sentence earns its place—there is no filler or redundancy. The examples are minimal and directly illustrate the key operations.

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?

For a tool with four parameters, multiple operations, and vault-selection logic, the description is remarkably complete. It covers the return value, examples for typical use cases, idempotency, and scope limitations. Nothing an agent needs to call the tool correctly is missing.

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?

The input schema already documents `op`, `path`, and `tags` with detailed descriptions, and the schema coverage is 75%. The description adds meaning to the undocumented `vaultPath` parameter by clarifying that it overrides the session active vault, and it reinforces the behavior of `merge` as an alias for `add`. The examples further illustrate parameter usage, so the description compensates for the missing schema coverage on `vaultPath`.

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 opens with a precise statement of purpose: 'Mutate the frontmatter `tags` list of a single note.' This gives a clear verb (mutate), resource (frontmatter tags), and scope (single note), and it immediately distinguishes this from read-only sibling tools like `tags.search` and `tags.list`. The supported operations (add, remove, replace, merge) are explicitly enumerated, leaving no ambiguity about what the tool does.

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 explains how vault selection works ('Operates on the session-active vault ... unless an explicit `vaultPath` is passed') and that it only touches frontmatter, implying that inline tag editing would require a different tool. However, it does not explicitly name alternative tools for those cases, and it does not state when to use this over other tag-related tools like `tags.search`. The guidance is present but implicit rather than explicit.

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

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/bezata/kObsidian'

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