@drmaxbdc/productboard-mcp

set_entity_parent

Replace or assign the parent of a Productboard entity using child and new parent UUIDs. Use it to update hierarchy relationships when an item's parent changes.

Instructions

Set or replace the parent of a Productboard entity. Uses PUT to replace any existing parent relationship.

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": {
      "entityId": "<entityId>",
      "parentId": "<parentId>"
    },
    "name": "set_entity_parent"
  }
}

Input Schema

Name	Required	Description	Default
`entityId`	Yes	Child entity UUID
`parentId`	Yes	New parent entity UUID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.1Sep 13, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the operation uses PUT and replaces any existing parent relationship, but it does not cover permissions, side effects, reversibility, or what happens if the parent is invalid.

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?

The description is two short sentences with no wasted words. The core purpose is front-loaded, followed immediately by the replacement behavior.

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?

For a simple two-parameter mutation with full schema descriptions and no output schema, the description is nearly complete: it states the operation and the replace semantics. It leaves minor gaps around authorization and error behavior, but no annotation or output schema requires further explanation.

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%, and both parameters are documented in the schema as UUIDs for child and new parent. The description adds no parameter meaning beyond what the schema already provides, so the baseline of 3 applies.

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 states a specific verb+resource: it sets or replaces the parent of a Productboard entity. This is clearly distinguishable from sibling tools like create_entity_relationship or update_entity because it directly names the parent-linking operation.

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

Usage Guidelines3/5

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

It implies usage by saying 'Set or replace the parent,' which tells the agent this is the tool for assigning a parent. However, it does not explicitly say when to choose this over alternatives such as create_entity_relationship, nor does it state any exclusions or prerequisites.

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