Skip to main content
Glama

renameTag

Update a tag's name in all bookmarks or within a specific collection in Raindrop.io. Provide the current and new tag names for efficient organization.

Instructions

Rename a tag across all bookmarks or in a specific collection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionIdNoCollection ID (optional)
newNameYesNew tag name
oldNameYesCurrent tag name

Implementation Reference

  • Core handler function implementing the renameTag logic via Raindrop.io API PUT request to rename a tag.
    async renameTag(collectionId: number | undefined, oldName: string, newName: string): Promise<boolean> {
      const endpoint = collectionId ? '/tags/{collectionId}' : '/tags/0';
      const options = {
        ...(collectionId && { params: { path: { id: collectionId } } }),
        body: { from: oldName, to: newName }
      };
      const { data } = await (this.client as any).PUT(endpoint, options);
      return !!data?.result;
    }
  • Handler logic within the 'tag_manage' MCP tool for the 'rename' operation, which delegates to the renameTag service method.
        if (!args.tagNames || !args.newName) throw new Error('tagNames and newName required for rename');
        const [primaryTag] = args.tagNames;
        if (!primaryTag) throw new Error('tagNames must include at least one value');
        return await raindropService.renameTag(args.collectionId, primaryTag, args.newName!);
    case 'merge':
  • Zod input schema for tag management operations, supporting 'rename' with collectionId, tagNames, newName.
    export const TagInputSchema = z.object({
        collectionId: z.number().optional(),
        tagNames: z.array(z.string()),
        newName: z.string().optional(),
        operation: z.enum(["rename", "merge", "delete"]),
    });
  • Declarative registration/configuration of the 'tag_manage' MCP tool that encompasses the renameTag functionality via operation='rename'.
    const tagManageTool = defineTool({
        name: 'tag_manage',
        description: 'Renames, merges, or deletes tags. Use the operation parameter to specify the action.',
        inputSchema: TagInputSchema,
        outputSchema: TagOutputSchema,
        handler: handleTagManage,
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the action ('Rename a tag') but doesn't disclose behavioral traits such as whether it requires specific permissions, if it's idempotent, what happens to bookmarks with the old tag, error conditions (e.g., duplicate new names), or response format. This is a significant gap for a mutation tool with zero annotation coverage.

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, efficient sentence that front-loads the core action ('Rename a tag') and adds necessary scope information. There is zero waste, and every word earns its place, making it easy to parse quickly.

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 complexity (a mutation tool with 3 parameters), no annotations, and no output schema, the description is incomplete. It lacks details on behavioral aspects (e.g., permissions, errors, effects), doesn't fully explain parameter usage beyond schema hints, and provides no information on return values or side effects, leaving significant gaps for an AI agent.

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 schema already documents all parameters (oldName, newName, collectionId). The description adds minimal value by hinting at the scope ('across all bookmarks or in a specific collection'), which relates to the optional 'collectionId', but doesn't provide additional syntax, format details, or constraints beyond what the schema offers. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('a tag'), specifying the scope ('across all bookmarks or in a specific collection'). It distinguishes from siblings like 'deleteTag', 'mergeTags', or 'bulkTagBookmarks' by focusing on renaming rather than deletion, merging, or bulk operations. However, it doesn't explicitly contrast with 'mergeTags' (which might involve renaming during merging), leaving slight ambiguity.

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 usage by mentioning the scope ('across all bookmarks or in a specific collection'), suggesting it can be used broadly or narrowly. However, it lacks explicit guidance on when to use this vs. alternatives like 'mergeTags' (for combining tags) or 'deleteTag' (for removal), and doesn't specify prerequisites (e.g., tag existence) or exclusions (e.g., invalid names).

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

Related 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/adeze/raindrop-mcp'

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