Skip to main content
Glama

bear_delete_tag

DestructiveIdempotent

Delete a tag from all Bear notes. Removes the tag text while preserving the notes.

Instructions

Delete a tag from all Bear notes. The tag text is removed but notes are preserved.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagYesTag to delete (without #)

Implementation Reference

  • Tool definition and schema for bear_delete_tag: defines the tool name, description, inputSchema (requires a 'tag' string), and annotations (destructiveHint: true).
    bear_delete_tag: {
      tool: {
        name: "bear_delete_tag",
        description:
          "Delete a tag from all Bear notes. The tag text is removed but notes are preserved.",
        inputSchema: {
          type: "object" as const,
          properties: {
            tag: {
              type: "string",
              description: "Tag to delete (without #)",
            },
          },
          required: ["tag"],
        },
        annotations: {
          readOnlyHint: false,
          destructiveHint: true,
          idempotentHint: true,
        },
      },
      buildArgs: (input) => [
        "tag",
        "delete",
        String(input.tag),
        "--json",
      ],
  • Handler for bear_delete_tag: the buildArgs function constructs the CLI arguments ['tag', 'delete', '<tag>', '--json'] which are executed by index.ts via execBcliWithReauth.
    buildArgs: (input) => [
      "tag",
      "delete",
      String(input.tag),
      "--json",
    ],
  • The tools object (Record<string, ToolHandler>) registers all tools including bear_delete_tag, which is then imported and used by index.ts for listing and calling tools.
    export const tools: Record<string, ToolHandler> = {
Behavior4/5

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

Annotations already indicate destructive and idempotent. Description adds value by clarifying notes are preserved, which resolves potential ambiguity. No contradiction.

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?

Two concise sentences with no redundant information. Perfect front-loading of action and effect.

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 simple delete operation, all necessary information is present: purpose, effect, parameter format. Output schema not needed. Annotations and siblings provide 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 provides 100% description coverage including the 'without #' convention. Description adds no additional meaning beyond schema.

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?

Clearly states the verb 'Delete' and resource 'tag' with scope 'from all Bear notes'. Implicitly distinguishes from sibling bear_remove_tag by global scope, but does not explicitly compare.

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 on when to use this tool vs alternatives like bear_remove_tag or bear_rename_tag. The description only states functionality without usage context.

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

Install Server

Other Tools

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/KuvopLLC/better-bear'

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