FeatureOS

Merge posts

merge_posts

Destructive

Merge one or more posts into a parent post, consolidating votes, comments, and subscribers.

Up to 30 posts can be merged at once. Requires an organization member (admin or team member) — the child posts' votes, comments, and subscribers are moved onto the parent, and the children become merged child posts.

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": {
      "feature_request_id": "<feature_request_id>",
      "child_feature_request_ids": "<child_feature_request_ids>"
    },
    "name": "merge_posts"
  }
}

Input Schema

Name	Required	Description	Default
`feature_request_id`	Yes	The ID of the parent post to merge the child posts into.
`child_feature_request_ids`	Yes	Post IDs to merge into the parent. Pass as a JSON array of integers, e.g. [4231, 4232]. Do NOT pass a quoted string. Maximum of 30 posts per request.

Output Schema

Name	Required	Description	Default
`feature_request`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description goes beyond them by spelling out the actual state change: child votes, comments, and subscribers are moved onto the parent and the children become merged child posts. It also adds the authorization requirement and the 30-post ceiling. The one gap is whether the operation is reversible (unmerge_post exists as a sibling but is never mentioned).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is front-loaded and the prerequisite/limit follow immediately, so an agent gets the essentials in one pass. There is mild redundancy — 'votes, comments, and subscribers' is stated twice and 'up to 30 posts' duplicates the schema — which keeps it short of a 5.

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 two-parameter destructive mutation with an output schema and full annotation coverage, the description supplies the missing pieces: permission requirement, batch cap, and the post-merge state of children. Only the reversibility question and any partial-failure behavior remain unaddressed.

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 the schema already documents the parent/child roles, the JSON-array format, the example, and the 30-post maximum. The description restates the same 30-post limit and the same consolidation targets, adding little semantic meaning beyond the structured fields, so the baseline 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 names a specific verb and resource (merge posts into a parent post) plus the consolidated entities (votes, comments, subscribers), which distinguishes it from siblings like unmerge_post and list_merged_posts without needing to open a schema.

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?

It states a concrete precondition (must be an organization member — admin or team member) and a hard batch limit (up to 30 posts), which tells the agent when the call is permissible. It does not name unmerge_post as the reversal path or state when to prefer merging over other consolidation approaches, so it stops short of full alternative routing.

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

All FeatureOS tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.