@drmaxbdc/productboard-mcp

update_entity

Update an existing Productboard entity using fields for simple replacement or patch operations for granular set, add, remove, or clear changes.

Instructions

Update an existing Productboard entity. Use 'fields' for simple field replacement, or 'patch' for granular operations (set, addItems, removeItems, clear). These are mutually exclusive. Note: addItems/removeItems on 'teams' is emulated client-side (read-merge-set) due to a PB API bug.

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": {
      "id": "<id>"
    },
    "name": "update_entity"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Entity UUID to update
`patch`	No	Granular patch operations. Mutually exclusive with fields.
`fields`	No	Fields to replace (simple update). Mutually exclusive with patch.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.1Sep 13, 2026

TDQS

A3.9/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses a genuinely non-obvious behavioral quirk: addItems/removeItems on 'teams' is emulated client-side via read-merge-set due to a PB API bug, plus the mutual-exclusivity constraint. It still omits permission requirements, reversibility, and error/partial-failure behavior for a mutation tool.

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?

Three front-loaded sentences, each carrying distinct information: purpose, mode selection, and a behavioral caveat. No filler or restatement of the name.

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?

For a mutation tool with no annotations and no output schema, the description covers mode selection and a key quirk but leaves out permission/auth requirements, what a successful update returns, and how failures or conflicts are surfaced. Adequate but with clear gaps.

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 id, patch ops, and fields. The description reinforces the fields/patch distinction and adds the teams workaround note, but the mutual-exclusivity it mentions is already stated in the schema's own field descriptions, so added value is marginal over the baseline.

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 clear verb+resource: 'Update an existing Productboard entity.' This distinguishes it from create_entity/delete_entity/get_entity siblings, though it doesn't explicitly name them. The scope of the update is well defined via the two modes.

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?

Clearly tells the agent when to use 'fields' (simple replacement) vs 'patch' (granular ops) and flags them as mutually exclusive. No exclusions around when not to use this tool versus sibling mutations, but the mode-selection guidance is explicit.

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