Skip to main content
Glama
bruhsb
by bruhsb

paperclip_list_heartbeat_runs

Read-only

List heartbeat runs for your company to audit agent execution or diagnose heartbeat failures. Optionally filter by agent.

Instructions

⚠ Board-only: List heartbeat runs for the company, optionally filtered by agent.

Args:

  • companyId: string — Company UUID (example: "53caad5d-05d6-469d-b6eb-8961a71b615e")

  • agentId: string (optional) — Filter runs to a specific agent UUID (example: "agt_abc123")

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

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

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

Returns: Pagination envelope { items: HeartbeatRun[], total, count, offset, limit, has_more, next_offset }. Each item: id, agentId, status, startedAt, finishedAt.

Examples:

  • Use when: auditing recent agent execution runs or diagnosing agent heartbeat failures

  • Don't use when: you need the raw event stream for a specific run — use paperclip_list_run_events instead

Error Handling:

  • 401: authentication failed → check PAPERCLIP_API_KEY

  • 403: permission denied → board-only endpoint, requires board API key

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyIdYesCompany UUID
agentIdNoFilter by agent UUID (optional) — omit to list runs across all agents
limitYesMax runs per page (1–100, default 50)
offsetYesNumber of runs 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?

Disclosures include board-only auth requirement, pagination behavior, error handling (401, 403), and return format options. Annotations already indicate readOnlyHint, so 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with sections for purpose, parameters, returns, examples, and error handling. A bit lengthy but each part adds value.

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?

Considering 5 parameters, no output schema, and many siblings, the description covers all essential aspects: purpose, usage, parameters (with examples), return envelope, error codes, and alternative 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% and descriptions are already comprehensive. The tool description adds examples and context but does not significantly enhance parameter meaning beyond the 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?

The description clearly states 'List heartbeat runs' with specific resource and filtering options. It distinguishes from sibling 'paperclip_list_run_events' by noting when not to use it.

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 when to use (auditing runs, diagnosing failures) and when not to use (raw event stream) with alternative tool named. Also warns about board-only access.

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