Skip to main content
Glama
bruhsb
by bruhsb

paperclip_list_projects

Read-only

Retrieve all projects for your company in markdown or JSON format to find project IDs for linking issues.

Instructions

List all projects for the current company.

Args:

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

Returns: Pagination envelope { items: Project[], total, count, offset, limit, has_more, next_offset }. Each item: id, name, status, goalId, createdAt.

Examples:

  • Use when: finding the projectId to link when creating a new issue

  • Don't use when: you need a project's workspaces — use paperclip_get_project or paperclip_list_workspaces

Error Handling:

  • 401: authentication failed → check PAPERCLIP_API_KEY

  • 403: permission denied → verify PAPERCLIP_COMPANY_ID is correct

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitYesMax projects per page (1–100, default 50)
offsetYesNumber of projects 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 show readOnlyHint=true; description adds return pagination envelope structure and error handling (401, 403) which inform agent behavior. Could mention ordering or scope beyond 'current company' but still adds value.

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?

Description is structured with clear sections (Args, Returns, Examples, Error Handling) but includes some redundancy (e.g., 'List all projects' and then 'Returns...'). Could be slightly tighter but is well organized.

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?

Given no output schema, description provides full return envelope structure. Includes error handling and usage examples. All parameters are described in schema, and description adds extra usage guidance. Complete for an agent to use correctly.

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 covers all 3 parameters 100%, but description adds context like response_format meaning and default, and explains the pagination envelope (which is not in input schema). This compensates for missing output schema.

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 clearly states it lists projects for the current company, with specific verb 'list' and resource 'projects'. It distinguishes from siblings like paperclip_get_project (single project) and paperclip_list_workspaces (workspaces vs projects) via the 'Don't use when' example.

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' (finding projectId to link issues) and 'Don't use when' (needing workspaces, with alternative tool names). This differentiates from many sibling tools.

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