Skip to main content
Glama
bruhsb
by bruhsb

paperclip_list_issues

Read-only

Retrieve a paginated list of issues for your company, filterable by status, assignee, project, goal, label, or full-text search.

Instructions

List issues for the current company with filtering and pagination.

Args:

  • status: string (optional) — Comma-separated statuses (example: "todo,in_progress")

  • assigneeAgentId: string (optional) — Filter by assignee agent UUID (example: "agt_abc")

  • projectId: string (optional) — Filter by project UUID

  • goalId: string (optional) — Filter by goal UUID

  • labelId: string (optional) — Filter by label UUID

  • q: string (optional) — Full-text search query (example: "auth bug")

  • limit: integer (optional) — Max results to return, 1–100 (default 50)

  • offset: integer (optional) — Skip N results for pagination (default 0)

Returns: Pagination envelope { items: Issue[], total, count, offset, limit, has_more, next_offset } with up to 50 issues per page (default, max 100).

Examples:

  • Use when: scanning the board for todo issues assigned to a specific agent

  • Don't use when: you need a single issue's full details — use paperclip_get_issue instead

Error Handling:

  • 401: authentication failed → check PAPERCLIP_API_KEY

  • 403: permission denied → verify PAPERCLIP_COMPANY_ID is correct

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoComma-separated status values (e.g. 'todo,in_progress')
assigneeAgentIdNoFilter by assignee agent ID
projectIdNoFilter by project ID
goalIdNoFilter by goal ID
labelIdNoFilter by label ID
qNoFull-text search query
limitYesMaximum number of issues to return (1–100, default 50)
offsetYesNumber of issues to skip before returning results (default 0)
response_formatYesOutput format: 'markdown' (default, human-readable) or 'json' (structured)markdown
Behavior5/5

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

Annotations already set readOnlyHint=true, and description adds details on pagination envelope, result limits, and error codes. 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-structured with sections for Args, Returns, Examples, Error Handling. However, it redundantly restates parameter descriptions that are already in the schema, slightly reducing conciseness.

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?

Comprehensive for a list tool with many filters and pagination. Describes return format (pagination envelope) despite no output schema. Includes error handling and practical examples.

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 has 100% coverage; description repeats most parameter descriptions verbatim but adds example values and usage context like comma-separated status. Does not significantly enhance beyond 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?

Clearly states 'List issues for the current company with filtering and pagination.' Distinguishes from sibling 'paperclip_get_issue' which retrieves a single issue. Verb+resource+scope are specific.

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?

Explicitly provides 'Use when' and 'Don't use when' examples, including the alternative tool name. Also covers error handling for common auth/permission issues.

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