Skip to main content
Glama
bruhsb
by bruhsb

paperclip_list_agents

Read-only

List all agents in your company with pagination support to resolve agent names to UUIDs for issue assignment or heartbeat operations.

Instructions

List all agents in the current company.

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

Examples:

  • Use when: resolving an agent name to a UUID before assigning an issue or invoking a heartbeat

  • Don't use when: you need full agent details — use paperclip_get_agent with the resolved ID

Error Handling:

  • 401: authentication failed → check PAPERCLIP_API_KEY

  • 403: permission denied → verify PAPERCLIP_COMPANY_ID is correct

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitYesMax agents per page (1–100, default 50)
offsetYesNumber of agents to skip (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?

Beyond annotations (readOnlyHint), the description details pagination behavior, return envelope structure, and error codes. No contradictions with 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?

Three concise paragraphs: purpose, return format, usage guidance with errors. No wasted words, front-loaded key details.

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?

Complete for a list tool: explains return shape, pagination limits, and error conditions. No output schema is needed given the thorough textual description.

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 description coverage is 100%, so baseline is 3. The description adds no additional parameter semantics beyond the schema, but is adequate.

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 it lists agents in the current company. Examples provide specific use cases and differentiate from similar tools like paperclip_get_agent.

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 to appropriate contexts, including a direct sibling alternative (paperclip_get_agent). Error handling adds further clarity.

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