Skip to main content
Glama
Sign In
Obsidian MCP Server

Obsidian MCP Server

by JujiuYey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

add_tag

Add a tag to a note in Obsidian by entering the note path and the tag. The tool updates the note's tags directly.

Instructions

Add a tag to a note

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": {
      "path": "<path>",
      "tag": "<tag>"
    },
    "name": "add_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYesTag to add
pathYesPath to the note

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It does not mention whether existing tags are preserved, if the note must already exist, whether duplicate tags are allowed, or any side effects.

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 a single, concise sentence that immediately conveys the action. Every word is functional, with no unnecessary information.

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?

For a simple add operation, the description is minimally adequate but lacks important context such as return values, error conditions, or idempotency behavior. With no annotations and no output schema, it does not fully cover the tool's behavior.

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?

The input schema fully describes both parameters (path and tag) with 100% coverage. The description adds no additional semantic meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 'Add a tag to a note' uses a specific verb and resource, clearly indicating the operation. It distinguishes from siblings like remove_tag, get_tag_notes, and search_by_tag, which have different purposes.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like update_note, which might also add tags, or remove_tag for the opposite operation. There are no exclusions or context cues beyond the basic action.

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