@drmaxbdc/productboard-mcp

list_all_notes

Bulk-fetch up to 5,000 Productboard notes via V2 API with auto-pagination and filters for archived, processed, owner, source, and date ranges.

Instructions

Bulk-fetch Productboard notes via V2 API with auto-pagination (~100/page). Safety limit: 5000 notes max. DEFAULT: returns processed + unprocessed notes that are NOT archived. To include archived notes set archived=true. V2 response shape: each note has top-level {id, type, links{self,html}, fields{...}, relationships{...}, createdAt, updatedAt, metadata}. NOTE: v2 no longer returns followers[], embedded comments, totalResults, or features[].importance. Use links.html in place of v1 displayUrl. Linked features are now under /notes/{id}/relationships (not inline) — use get_note_relationships per note if you need them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_all_notes"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Safety limit (default 5000)
`archived`	No	Filter by archived status. Default: false (archived notes are hidden). Set true to include or to fetch only archived notes.
`createdTo`	No	ISO 8601 date-time — notes created on/before (inclusive)
`processed`	No	Filter by processed status (true=processed, false=unprocessed). Default: both.
`updatedTo`	No	ISO 8601 date-time — notes updated on/before (inclusive)
`ownerEmail`	No	Filter by owner email. Requires members:pii:read scope on the access token.
`createdFrom`	No	ISO 8601 date-time — notes created on/after (inclusive)
`updatedFrom`	No	ISO 8601 date-time — notes updated on/after (inclusive)
`sourceSystem`	No	Filter by metadata.source.system (v2 equivalent of v1 source.origin). NOTE: source metadata may be empty during the v1→v2 transition; use only if you've verified data is populated for your workspace.
`sourceRecordId`	No	Filter by metadata.source.recordId.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.1Sep 13, 2026

TDQS

A4.1/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses auto-pagination (~100/page), a hard 5000-note safety cap, default filtering behavior, and concrete v2 response-shape details including what no longer exists (followers, comments, totalResults, features[].importance) and the migration path for displayUrl and linked features.

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?

Front-loaded with the core operation, pagination and safety limit, then defaults, then response shape. It is dense but each sentence conveys actionable information; the v1→v2 migration notes are long but relevant for correct data interpretation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by describing the v2 note shape and the relationship/migration caveats, which is exactly what an agent needs to consume results. Minor gaps remain around rate limits or ordering, but nothing critical is missing.

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 the schema already documents all ten parameters, including defaults and the members:pii:read scope for ownerEmail. The description largely restates the archived/processed defaults and adds no syntax or interpretation beyond the schema, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Bulk-fetch Productboard notes via V2 API') with an explicit scope qualifier ('bulk-fetch') that hints at a paginated list operation. It does not explicitly contrast itself with the sibling list_notes or search_notes, so an agent still has to infer which listing tool to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear defaults (processed+unprocessed, non-archived) and tells the agent how to include archived notes. It also names an alternative tool with a condition ('use get_note_relationships per note if you need them'). It stops short of distinguishing this tool from list_notes or search_notes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.