Skip to main content
Glama
bigjeager

Bear App MCP Server

by bigjeager

bear_rename_tag

Change an existing tag's name in Bear App to update organization and maintain consistency across notes.

Instructions

Rename an existing tag

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCurrent tag name
new_nameYesNew tag name
show_windowNoShow Bear window

Implementation Reference

  • The handler function that implements the bear_rename_tag tool logic by constructing a Bear x-callback-url for the 'rename-tag' action with old and new tag names, executing it via open command, and returning a success message.
    private async renameTag(args: any) {
      const params: Record<string, string | boolean> = {
        name: args.name,
        new_name: args.new_name
      };
      
      if (args.show_window) params.show_window = "yes";
    
      const url = this.buildBearURL("rename-tag", params);
      await this.executeURL(url);
    
      return {
        content: [
          {
            type: "text",
            text: `Renamed tag from "${args.name}" to "${args.new_name}"`
          }
        ]
      };
    }
  • Input schema definition for the bear_rename_tag tool, specifying required 'name' and 'new_name' parameters.
    inputSchema: {
      type: "object",
      properties: {
        name: {
          type: "string",
          description: "Current tag name"
        },
        new_name: {
          type: "string",
          description: "New tag name"
        },
        show_window: {
          type: "boolean",
          description: "Show Bear window"
        }
      },
      required: ["name", "new_name"]
  • src/index.ts:656-677 (registration)
    Registration of the bear_rename_tag tool in the ListTools response, including name, description, and input schema.
    {
      name: "bear_rename_tag",
      description: "Rename an existing tag",
      inputSchema: {
        type: "object",
        properties: {
          name: {
            type: "string",
            description: "Current tag name"
          },
          new_name: {
            type: "string",
            description: "New tag name"
          },
          show_window: {
            type: "boolean",
            description: "Show Bear window"
          }
        },
        required: ["name", "new_name"]
      }
    },
  • src/index.ts:733-734 (registration)
    Dispatch case in the CallToolRequestSchema handler that routes bear_rename_tag calls to the renameTag method.
    case "bear_rename_tag":
      return await this.renameTag(args);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It states the action ('rename') but doesn't cover permissions needed, whether the change affects linked notes, error conditions (e.g., if the tag doesn't exist or new_name conflicts), or response format. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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, direct sentence with zero wasted words, making it highly concise and front-loaded. Every word ('rename', 'existing', 'tag') contributes essential meaning, and there's no redundant or verbose phrasing. This efficiency aids quick comprehension by an AI agent.

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?

Given the tool's complexity (a mutation operation with no annotations and no output schema), the description is incomplete. It lacks details on behavioral traits (e.g., side effects, error handling), usage context, and return values, which are critical for safe and effective invocation. The high schema coverage doesn't compensate for these gaps in a tool that modifies data.

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 description coverage is 100%, so the input schema fully documents all three parameters (name, new_name, show_window) with clear descriptions. The tool description adds no additional parameter semantics beyond what's in the schema, such as format examples or constraints like character limits. This meets the baseline score of 3 when schema coverage is high.

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?

The description clearly states the verb ('rename') and resource ('an existing tag'), making the tool's purpose immediately understandable. It distinguishes this from sibling tools like 'bear_delete_tag' and 'bear_get_tags' by focusing on modification rather than deletion or retrieval. However, it doesn't specify what system or application the tag belongs to (Bear notes app), which would make it fully specific.

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?

The description provides no guidance on when to use this tool versus alternatives like 'bear_delete_tag' for removal or 'bear_get_tags' for listing. It doesn't mention prerequisites (e.g., the tag must exist) or contextual constraints, leaving the agent to infer usage from the tool name alone. This lack of explicit when/when-not instructions limits its effectiveness.

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/bigjeager/bear-mcp-server'

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