Skip to main content
Glama

bookmark_rename

Rename a bookmark or clear its label by omitting the new name; identify the saved item by its ID.

Instructions

Give a bookmark a name, or drop the one it has by omitting name.

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": {
      "id": "<id>"
    },
    "name": "bookmark_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesBookmark id from bookmark_list
nameNoNew label. Omit to remove the name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it mostly restates the schema's own 'Omit to remove the name' note. It says nothing about whether renaming is idempotent, what happens if the id is absent, whether an existing name is overwritten, or what the call returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence that front-loads the primary action and then the alternate mode. Nothing is wasted, though 'drop the one it has' is slightly more roundabout than 'remove the name'.

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 two-parameter tool with no output schema, the description covers both modes adequately. It leaves gaps on error behavior and on whether the tool is create-if-missing or strictly updates an existing bookmark, which matters when id is required.

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%, with both id (source: bookmark_list) and name (omit to remove) already documented in the schema. The description adds no format, length, or validation detail beyond what the schema supplies, so the baseline of 3 applies.

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 names a specific verb and resource (give a bookmark a name) and covers both the set and clear modes, so an agent can tell it is the rename tool. It does not explicitly contrast with nearby siblings like bookmark_add or bookmark_clear, so it stops short of a 5.

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 two usage modes are clear: supply a name to label the bookmark, omit it to strip the label. There is no explicit guidance on when to pick this over bookmark_add (creating) or bookmark_clear, nor any prerequisite such as the bookmark having to exist.

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