Skip to main content
Glama
bruhsb
by bruhsb

paperclip_list_run_events

Read-only

Stream run events for a heartbeat run using a cursor-based afterSeq to resume streaming from a specific sequence number.

Instructions

⚠ Board-only: Stream events for a heartbeat run using an afterSeq cursor (not paginated — cursor-based).

Args:

  • runId: string — Heartbeat run UUID (example: "run_abc123")

  • afterSeq: number (optional) — Return events with seq > afterSeq to resume streaming (default: 0)

  • limit: number (optional) — Max events to return in one call (default 100)

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

Returns: Array of run events (no pagination envelope — use afterSeq cursor for continuation). Each event: seq, type, data, createdAt.

Examples:

  • Use when: streaming execution events for a live or recently completed heartbeat run using the afterSeq cursor

  • Don't use when: you need raw log bytes — use paperclip_get_run_log with offset/limitBytes instead

Error Handling:

  • 401: authentication failed → check PAPERCLIP_API_KEY

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

  • 404: run not found → verify runId with paperclip_list_heartbeat_runs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
runIdYesHeartbeat run UUID
afterSeqNoReturn events with sequence number > afterSeq (cursor for streaming, default: 0 / start of run)
limitYesMax events to return (default 100) — note: cursor-based, not paginated
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, but the description adds specific behavioral details: cursor-based streaming, no pagination envelope, board-only auth requirements, and error codes with causes (401, 403, 404). This adds significant context beyond annotations.

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?

The description is well-structured with clear sections (header, args, returns, examples, error handling) but is somewhat lengthy; still, the information is efficiently organized and front-loaded.

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, the description fully covers the return shape (array with seq, type, data, createdAt), error handling, auth requirements, and a clear alternative tool. It is complete for the tool's complexity.

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%, so the description adds minimal additional meaning. It restates defaults and examples but does not provide novel parameter details beyond the schema descriptions.

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 is for streaming events for a heartbeat run using a cursor, distinguishing it from raw log retrieval via paperclip_get_run_log. The verb 'stream events' and resource 'heartbeat run' are specific, and the not-paginated cursor-based nature is emphasized.

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 with a named alternative (paperclip_get_run_log), plus board-only requirement and error handling conditions provide clear context for when this tool should and should not be used.

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