Skip to main content
Glama
bruhsb
by bruhsb

paperclip_list_labels

Read-only

Fetch paginated labels with name, color, and ID to build a label taxonomy cache. Essential for mapping label names to UUIDs in subsequent calls.

Instructions

List all labels defined for the current company.

Args:

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

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

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

Returns: Pagination envelope { items: Label[], total, count, offset, limit, has_more, next_offset }. Each item: id, name, color (hex), createdAt.

Examples:

  • Use when: bootstrapping the label taxonomy at the start of a run to build a name→UUID cache

  • Don't use when: you already have the label UUID — pass it directly to the relevant tool

Error Handling:

  • 401: authentication failed → check PAPERCLIP_API_KEY

  • 403: permission denied → verify PAPERCLIP_COMPANY_ID is correct

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitYesMax labels per page (1–100, default 50)
offsetYesNumber of labels 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 indicate readOnlyHint=true. The description adds behavioral details about pagination (has_more, next_offset) and error handling (401, 403), which are beyond the annotations. No contradiction.

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 well-structured with clear sections (Args, Returns, Examples, Error Handling). It is concise without unnecessary verbosity, using bullet points for readability.

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

Completeness5/5

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

Despite lacking an output schema, the description fully documents the return structure (pagination envelope with fields) and error handling. All parameters are explained. This is complete for a list tool with good annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all parameters. The description adds slight extra context like 'markdown (default, human-readable)' and 'json (structured)', but essentially matches the schema. Not significantly beyond.

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 all labels defined for the current company', which is a specific verb-resource combination. It is distinct from sibling tools like 'paperclip_create_label' by indicating it is a listing operation.

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?

The description explicitly provides usage guidance with 'Use when: bootstrapping the label taxonomy...' and 'Don't use when: you already have the label UUID...', giving clear when-to-use and when-not-to-use scenarios.

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