@drmaxbdc/productboard-mcp

get_entity_relationships

Fetch all relationships for a Productboard entity—parent, child, link, blocking—with optional filters by type or target.

Instructions

Get all relationships for a Productboard entity (parent, children, links, blocking, etc.). Can optionally filter by relationship type or target.

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>"
    },
    "name": "get_entity_relationships"
  }
}

Input Schema

Name	Required	Description
`type`	No	Filter by relationship type (parent, child, link, isBlockedBy, isBlocking)
`entityId`	Yes	Entity UUID
`targetId`	No	Filter by target entity UUID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.1Sep 13, 2026

TDQS

A3.6/5.0

Behavior3/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. It discloses that all relationship types are returned and lists examples, implying a read-only operation, but it does not mention permissions, pagination, rate limits, or response shape.

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 sentences, front-loaded with the core purpose and followed by optional filter information. No filler or redundancy; every sentence earns its place.

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 read-only tool with 3 parameters all documented in the schema and no output schema, the description covers purpose, scope, and filtering. It is largely complete, though it omits pagination or limit behavior that an agent might need for a listing operation.

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 all three parameters (type, entityId, targetId) are already documented in the schema. The description's mention of filtering by relationship type or target duplicates the schema without adding syntax, format, or constraint details. 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 ('Get') and resource ('relationships') for a Productboard entity, and enumerates relationship kinds (parent, children, links, blocking). It distinguishes itself from get_entity by focusing on relationships rather than the entity itself, though it does not name a sibling alternative explicitly.

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?

The description says it can optionally filter by relationship type or target, which implies a usage pattern. However, there is no explicit guidance on when to use this tool versus alternatives like get_entity, list_entities, or the relationship-mutating siblings, nor any prerequisites or exclusions.

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