Plane MCP Server

get_release_changelog

Retrieve a release's changelog by providing its UUID. Always returns a changelog, creating an empty one if needed.

Instructions

Get a release's changelog. Each release has a single changelog, created empty on first access, so this always returns one.

Args: release_id: UUID of the release

Returns: The ReleaseChangelog. Its body comes back as a nested object.

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": {
      "release_id": "<release_id>"
    },
    "name": "get_release_changelog"
  }
}

Input Schema

Name	Required	Description	Default
`release_id`	Yes

Output Schema

Name	Required	Description	Default
`id`	No
`release`	No
`changelog`	No
`workspace`	No
`created_at`	No
`created_by`	No
`updated_at`	No
`updated_by`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.11Aug 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that the changelog is created empty on first access (a subtle side effect), always returns one result, and that the body is a nested object. This goes beyond a simple 'get' and informs the agent of potential behavior.

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 concise, well-structured with Args/Returns sections, and front-loads the core purpose. Every sentence adds value without fluff.

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

Completeness5/5

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

For a simple one-parameter retrieval tool, the description covers behavior, parameter semantics, and return shape. An output schema exists, so further detail isn't necessary. The description fully equips an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It explains release_id as 'UUID of the release', adding semantic meaning beyond the plain string type. While minimal, it fully covers the single parameter's purpose.

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 action ('Get a release's changelog') and clarifies the unique behavior ('Each release has a single changelog, created empty on first access, so this always returns one'). This clearly differentiates it from siblings like update_release_changelog.

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?

The description provides clear context about when this tool is applicable (retrieving a changelog, always returns one) but does not explicitly mention alternatives or exclusions. The behavior of returning a single changelog implies its use case, but no sibling comparison is given.

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

Deploy Server