@drmaxbdc/productboard-mcp

create_note

Create Productboard notes (insights) by supplying a type and field values. Call get_note_configurations first to discover available fields and note types.

Instructions

Create a new Productboard note (insight). Call get_note_configurations first to discover available fields and note types (simple, conversation).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>",
      "fields": "<fields>"
    },
    "name": "create_note"
  }
}

Input Schema

Name	Required	Description
`type`	Yes	Note type (simple or conversation). Opportunity notes cannot be created via API.
`fields`	Yes	Note field values. 'name' is required. Use get_note_configurations to discover all fields.
`relationships`	No	Optional relationships to create with the note

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.1Sep 13, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it only covers a workflow pointer. It says nothing about required permissions, side effects, whether the note is immediately visible, or error conditions for a mutation tool. The 'opportunity notes cannot be created via API' constraint lives only in the schema, not the description.

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?

Two short sentences with the action front-loaded and the prerequisite second. No filler; every clause earns its place.

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

Completeness3/5

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

The nested relationships object and mutation nature are non-trivial, and with no annotations and no output schema the description should disclose more about permissions, effects, and return shape. The prerequisite guidance is useful but leaves the behavioral picture incomplete.

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 type, fields, and relationships, including the enum and the 'name is required' rule. The description adds the pointer to get_note_configurations for field discovery, which is modest value over the schema. Baseline 3 is 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 and resource: 'Create a new Productboard note (insight)'. This is clearly distinguishable from the entity and relationship tools, though it doesn't explicitly contrast itself with create_entity or note-creation alternatives.

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?

Provides an explicit prerequisite workflow: 'Call get_note_configurations first to discover available fields and note types'. This tells the agent how to prepare, though it offers no when-not-to-use guidance or alternatives to create_note.

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