Skip to main content
Glama
anchor-notes-mcp

anchor-notes-mcp

by NatanaelJose

bulk_update_notes

Apply one action—trash, archive, pin, unpin, or add tags—to multiple Anchor notes at once, keeping existing tags when adding new ones.

Instructions

Apply one action to many notes at once: trash, archive, pin, unpin, or add_tags (adds tagIds, keeps existing tags).

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": {
      "noteIds": "<noteIds>",
      "action": "<action>"
    },
    "name": "bulk_update_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
tagIdsNoRequired for add_tags
noteIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=false and destructiveHint=false; the description adds useful context by spelling out that add_tags merges rather than replaces tags ('keeps existing tags'). It still omits what most matters for a bulk mutation: whether the operation is atomic or partially applies when some noteIds are invalid, and whether trash is recoverable. The 'trash' action alongside destructiveHint=false is consistent only if trash is a soft, restorable state, which the description never confirms.

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?

A single front-loaded sentence with the bulk scope first, the action list second, and the one non-obvious semantic (tag merge) parenthized at the end. Nothing is padded or restated.

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 bulk writer with no output schema, an agent still lacks failure/atomicity behavior and any sense of what the response reports for up to 200 notes. The description and annotations together cover the safety profile and action vocabulary adequately, but the mutation-specific behavior an agent needs before firing on 200 records is absent.

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?

With only 33% schema description coverage, the description partially compensates by naming all action values and stating that add_tags consumes tagIds and preserves existing tags, which clarifies the conditional requirement the schema cannot express structurally. It says nothing about noteIds, the primary required parameter (an array bounded at 200), nor about the tagIds cap of 50, so the gap is only half-closed.

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?

States a specific verb and resource ('apply one action to many notes at once') and enumerates all five actions (trash, archive, pin, unpin, add_tags). The phrase 'many notes at once' explicitly separates it from the singular update_note sibling, so an agent can pick between them without opening either schema.

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?

Bulk-vs-single usage is implied by 'many notes at once', which is enough to route an agent away from update_note. However, no alternative is named and there is no guidance on when to prefer trash_note/restore_note or when a bulk operation is inappropriate (e.g. heterogeneous actions).

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