Skip to main content
Glama

getTags

Retrieve all tags from your Raindrop.io collections to organize and manage bookmarks efficiently. Filter tags by collection to streamline your workflow.

Instructions

Get all tags

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionIdNoFilter tags by collection

Implementation Reference

  • The core handler function implementing getTags, which fetches tags from the Raindrop.io API for a specific collection (if provided) or all tags. Uses the OpenAPI client to make the appropriate GET request to /tags/{collectionId} or /tags/0.
    async getTags(collectionId?: number): Promise<{ _id: string; count: number }[]> {
      const endpoint = collectionId ? '/tags/{collectionId}' : '/tags/0';
      const options = collectionId
        ? { params: { path: { id: collectionId } } }
        : undefined;
      const { data } = await (this.client as any).GET(endpoint, options);
      return data?.items || [];
    }
  • Helper wrapper that calls getTags specifically for a collection ID.
    async getTagsByCollection(collectionId: number): Promise<{ _id: string; count: number }[]> {
      return this.getTags(collectionId);
    }
  • Zod schema defining the structure of tag objects returned by getTags.
    export const tagSchema = z.object({
        _id: z.string(),
        count: z.number().optional(),
        name: z.string().optional(),
    });
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 of behavioral disclosure. 'Get all tags' implies a read-only operation, but it doesn't specify if this requires authentication, returns paginated results, includes metadata like tag counts, or has rate limits. For a tool with zero annotation coverage, this leaves critical behavioral traits unaddressed.

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?

The description is extremely concise with just three words, making it front-loaded and efficient. However, it borders on under-specification—while not wasteful, it could benefit from slightly more detail to clarify scope or usage without losing brevity.

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 simplicity (1 optional parameter, no output schema, no annotations), the description is incomplete. It doesn't explain what 'tags' are in this system, what data is returned, or how it relates to sibling tools like those for bookmarks or collections. For a tool in a rich context with many siblings, more contextual information is needed.

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?

The input schema has 100% description coverage, with the parameter 'collectionId' documented as 'Filter tags by collection'. The description 'Get all tags' implies no filtering by default, which aligns with the optional nature of the parameter. Since schema coverage is high, the baseline score is 3, as the description adds minimal value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get all tags' is a tautology that restates the tool name 'getTags' without adding meaningful specificity. It doesn't distinguish this tool from sibling tools like 'mergeTags' or 'renameTag' by explaining what 'tags' are in this context or what 'get' entails. While it uses a clear verb+resource pattern, it lacks differentiation from alternatives.

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. It doesn't mention sibling tools like 'mergeTags' or 'renameTag' for tag management, nor does it explain if this is for listing, filtering, or retrieving tag metadata. There's no context on prerequisites, exclusions, or typical use cases.

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