Skip to main content
Glama
Sign In
Obsidian MCP Server

Obsidian MCP Server

by JujiuYey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

remove_tag

Remove a tag from a note in Obsidian by providing the note path and tag name.

Instructions

Remove a tag from 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": "remove_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYesTag to remove
pathYesPath to the note

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

Without annotations, the description carries full burden for behavioral disclosure. It only states the action but does not explain side effects, idempotency, error behavior, or whether the tag is also deleted globally. This is insufficient for a mutation tool.

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 is front-loaded with the core action. There is no redundancy or unnecessary detail.

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

Completeness2/5

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

The tool is simple, but the description omits critical details such as return values, error handling, and whether removing the tag has any side effects on the tag entity itself. With no annotations or output schema, the description should provide more behavioral context.

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 clear descriptions for both parameters (path and tag). The description adds minimal extra meaning beyond what the schema already provides, so a baseline 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 clearly states the action 'Remove a tag from a note' with a specific verb and resource. It distinguishes itself from siblings like add_tag and get_tag_notes by explicitly describing the inverse operation.

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?

The description implies its usage (when you need to remove a tag), but does not provide explicit guidance on when to use it vs. alternatives like update_note, nor does it mention any exclusions or prerequisites. The purpose is clear enough that usage is inferred.

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