Skip to main content
Glama
bruhsb
by bruhsb

paperclip_list_plugins

Read-only

Retrieve installed plugins for a Paperclip instance, filterable by lifecycle status and paginated. Audits plugin states or identifies errors.

Instructions

⚠ Board-only: List installed plugins for the Paperclip instance, with optional status filter.

Args:

  • status: enum (optional) — Filter by lifecycle status: installed | ready | disabled | error | upgrade_pending | uninstalled

  • limit: number (optional) — Max results per page (1–100, default 50)

  • offset: number (optional) — Number of records to skip (default 0)

  • response_format: 'markdown' | 'json' (optional) — Output format (default: markdown)

Returns: Pagination envelope { items: Plugin[], total, count, offset, limit, has_more, next_offset }. Each item: pluginKey, packageName, displayName, description, status, version.

Examples:

  • Use when: auditing which plugins are installed or filtering for plugins in error state

  • Don't use when: you need the full plugin detail (health, config) — use paperclip_get_plugin instead

Error Handling:

  • 401: authentication failed → check PAPERCLIP_API_KEY

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by plugin status (omit to return all statuses)
limitYesMax plugins per page (1–100, default 50)
offsetYesNumber of plugins to skip (default 0)
response_formatYesOutput format: 'markdown' (default, human-readable) or 'json' (structured)markdown
Behavior4/5

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

Annotations already provide readOnlyHint=true, so the bar is lower. The description adds '⚠ Board-only' (required API key type) and error handling details (401, 403), which enrich transparency beyond annotations. No contradictions.

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?

Well-organized with sections (Args, Returns, Examples, Error Handling), but somewhat lengthy. Every sentence adds value, though it could be more concise by omitting redundant schema details. Good front-loading of key info.

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?

Despite no output schema, the description explains the pagination envelope and field names, filling the gap. Error handling covers auth and permission scenarios. Missing details like rate limits, but adequate for a list tool.

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 the baseline is 3. The description repeats the enum values for status and defaults for limit/offset/response_format, adding no new semantic meaning beyond what the input schema provides.

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?

The description clearly states 'List installed plugins for the Paperclip instance', specifying a concrete verb and resource. It distinguishes from siblings like paperclip_get_plugin by noting the optional status filter and referencing the alternative for full detail.

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?

Explicit 'Use when' and 'Don't use when' sections guide the agent: use for auditing or filtering by error status, avoid when full plugin detail is needed (referring to paperclip_get_plugin). This is exemplary guidance.

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