Skip to main content
Glama
bruhsb
by bruhsb

paperclip_list_feedback_traces

Read-only

Retrieve company feedback traces with optional filters for type, vote, status, project, issue, and date range. Enables broad auditing and analysis across the organization.

Instructions

⚠ Board-only: List feedback traces for the company, with optional filters for type, vote, status, project, issue, date range, and payload inclusion.

Args:

  • companyId: string — Company UUID

  • targetType: string (optional) — Filter by target type

  • vote: string (optional) — Filter by vote value

  • status: string (optional) — Filter by trace status

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

  • issueId: string (optional) — Filter by issue ID

  • from: string (optional) — ISO 8601 datetime lower bound

  • to: string (optional) — ISO 8601 datetime upper bound

  • sharedOnly: boolean (optional) — Return only shared traces

  • includePayload: boolean (optional) — Include full trace payload

  • response_format: 'markdown' | 'json' (optional, default: markdown)

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

  • offset: number (optional) — Items to skip (default 0)

Returns: Pagination envelope { items: FeedbackTrace[], total, count, offset, limit, has_more, next_offset }.

Examples:

  • Use when: auditing feedback across the company or filtering by issue, vote, or date range

  • Don't use when: you need traces for a single issue — use paperclip_list_issue_feedback_traces

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
targetTypeNoFilter by target type (e.g. 'issue', 'comment')
voteNoFilter by vote value (e.g. 'up', 'down')
statusNoFilter by trace status (e.g. 'pending', 'resolved')
fromNoISO 8601 datetime — return traces created at or after this timestamp
toNoISO 8601 datetime — return traces created at or before this timestamp
sharedOnlyNoWhen true, return only traces marked as shared
includePayloadNoWhen true, include full trace payload in response
projectIdNoFilter by project UUID
issueIdNoFilter by issue ID or identifier
response_formatYesOutput format: 'markdown' (default, human-readable) or 'json' (structured)markdown
limitYesMax traces per page (1–100, default 50)
offsetYesNumber of traces to skip (default 0)
Behavior5/5

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

Disclosures beyond annotations include pagination details (limit, offset, has_more, next_offset), board-only endpoint requiring board API key, and error codes with explanations. No contradiction 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?

Description is well-organized with sections: summary, args, returns, examples, error handling. No unnecessary detail, front-loaded with warning. Efficient and clear.

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 13 parameters, pagination, and multiple filters, the description covers usage, all parameters, return envelope, and error handling. No output schema, but return format is described.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds structured parameter list with defaults, constraints, and formats (e.g., ISO 8601 for dates, 1-100 for limit), enhancing clarity.

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 the tool lists feedback traces for a company with optional filters. It distinguishes from the sibling tool paperclip_list_issue_feedback_traces by explicitly advising against using it for a single issue.

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?

Includes explicit 'Use when' and 'Don't use when' examples, points to alternative tool, and mentions board-only restriction and error handling, providing clear guidance.

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