Skip to main content
Glama
bruhsb
by bruhsb

paperclip_install_plugin

Install a plugin into the Paperclip instance from an npm package or local filesystem path.

Instructions

⚠ Board-only: Install a plugin from npm into the Paperclip instance.

Args:

  • packageName: string — npm package name (e.g. '@paperclipai/plugin-hello-world-example') or local filesystem path when isLocalPath is true

  • version: string (optional) — Specific version to install (e.g. '1.2.3'); omit for latest

  • isLocalPath: boolean (optional) — Set true when packageName is a local filesystem path

Returns: Installation result object with pluginKey, packageName, status, and message confirming the install outcome.

Examples:

  • Use when: adding a new plugin capability to the Paperclip instance from the npm registry or a local build

  • Don't use when: the plugin is already installed — use paperclip_enable_plugin to re-activate a disabled plugin

Error Handling:

  • 400: install failed (npm error) → verify packageName is a valid npm package that exists in the registry

  • 401: authentication failed → check PAPERCLIP_API_KEY

  • 403: permission denied → this tool requires a board (human-user) API key

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageNameYesnpm package name to install (e.g. '@paperclipai/plugin-hello-world-example')
versionNoSpecific package version to install (e.g. '1.2.3'); omit for latest
isLocalPathNoSet true when packageName is a local filesystem path rather than an npm package name
Behavior4/5

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

Annotations (destructiveHint=false, openWorldHint=true) are consistent. Description adds error handling details (400, 401, 403), return format, and auth requirements. It doesn't mention reversibility or side effects, but overall provides good behavioral context beyond annotations.

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?

Well-structured with sections for warning, args, returns, examples, and error handling. Front-loaded with important board-only warning. No redundant or unnecessary sentences; every part earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Comprehensive for a tool with no output schema: describes return object, error codes, and parameter details. Distinguishes from sibling tools. Could add more about version validation but error section covers npm errors adequately.

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 coverage is 100%, so baseline is 3. Description adds value by explaining that packageName can be a local filesystem path when isLocalPath is true, and that version is optional. However, this mostly restates schema descriptions without significant new insight.

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

Purpose5/5

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

Description explicitly states the tool installs a plugin from npm into Paperclip instance. It specifies 'board-only' access and distinguishes from sibling tools like paperclip_enable_plugin for reactivating disabled plugins. The verb 'install' and resource 'plugin' are clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit 'Use when' and 'Don't use when' statements, including a sibling tool alternative (paperclip_enable_plugin). Also mentions the tool requires a board API key. This gives clear guidance on appropriate usage.

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/bruhsb/paperclip-mcp'

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