Skip to main content
Glama
K-Jadeja

@kjadeja/open-featurebase-mcp

by K-Jadeja

list_featurebase_posts

Retrieve and filter feedback posts from a Featurebase board by status, sort order, and team reply presence. Specify team member IDs to classify admin responses.

Instructions

List posts on the configured Featurebase feedback board.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of posts to return (1-200).
sortByNoSort order for results.date:desc
statusNoFilter by Featurebase status. Values map to underlying postStatus.type as: in_review → 'reviewing', planned → 'unstarted', in_progress → 'active', completed → 'completed', open → 'open'.all
teamUserIdsNoOptional override for the team-user-id set. When provided as a NON-EMPTY array, this list of IDs is treated as the team for hasAdminReply classification, REPLACING the FEATUREBASE_TEAM_USER_IDS env var for this call only. An EMPTY array ([]) is treated as ABSENT — the env var is used if configured, otherwise the request still fails with InvalidParams for hasAdminReply. Useful after a find_featurebase_user drill-down — pass the returned userIds here to filter the listing by team engagement without re-reading the env.
hasAdminReplyNoWhen true, restrict to posts where the team has authored at least one comment (hasAdminReply === true). When false, restrict to posts where the team has NOT commented. REQUIRES a team identity — if no team is available (FEATUREBASE_TEAM_USER_IDS unset AND no teamUserIds override supplied), the request FAILS with InvalidParams rather than silently returning an empty list. Fabricating hasAdminReply=false for every post would be a silent false-positive for callers asking for hasAdminReply:false, and a silent false-negative for callers asking for hasAdminReply:true. Call find_featurebase_user first to discover user IDs, then pass them as teamUserIds.
Behavior2/5

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

No annotations are provided, and the description lacks details on behavioral traits such as rate limits, authentication requirements, or potential side effects. It assumes a 'configured' board without explaining setup.

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 own description is concise, but extensive parameter details follow. The structure is front-loaded with the core purpose and then detailed parameter info, which is appropriate.

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?

While parameter documentation is thorough, the description omits output format, pagination details beyond limit, and error scenarios. Given the lack of output schema, more completeness on return values is needed.

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?

The schema already covers parameters fully (100% coverage). The description adds significant value by explaining complex behaviors of teamUserIds and hasAdminReply, especially the override logic and error handling.

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?

The description clearly states it lists posts from the configured Featurebase board. However, it does not differentiate from sibling tools like get_featurebase_posts or search_featurebase_posts, which likely have similar listing capabilities.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. The description does not mention prerequisites, when not to use, or any context for selection among siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/K-Jadeja/open-featurebase-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server