Skip to main content
Glama
thenavidm

Fluent WordPress MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

fc list feeds

fc_list_feeds
Read-onlyIdempotent

List paginated feed posts the current user can read, with pinned space post separated on the first page; supports page, space, status, and search filters.

Instructions

Returns a page of posts the current user is allowed to read, transformed for display, with the pinned post of a space returned separately on the first page.

Controller: FeedsController@get Route source: fluent-community/app/Http/Routes/api.php:45

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage read via `$request->get()` in get().
spaceNoSpace read via `$request->get()` in get().
searchNoSearch read via `$request->getSafe()` in get().
statusNoStatus read via `$request->getSafe()` in get().
accountNoExact configured private account profile label; not a tenant or provider account ID.
user_idNoUser ID read via `$request->getSafe()` in get().
per_pageNoPer Page read via `$request->get()` in get().
search_inNoSearch In read via `$request->get()` in get().
topic_slugNoTopic Slug read via `$request->getSafe()` in get().
order_by_typeNoOrder By Type read via `$request->getSafe()` in get().
disable_stickyNoDisable Sticky read via `$request->get()` in get().

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds genuinely useful behavior: results are permission-filtered ('current user is allowed to read'), transformed for display, paginated ('a page'), and the space's pinned post is surfaced separately on the first page only. That pinned-post edge case is non-obvious and valuable.

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 information-dense with no filler. The two trailing controller/route lines are developer metadata that do not help an agent invoke the tool, which slightly dilutes an otherwise tight definition.

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?

With no output schema, the description still sketches the return shape (a page of display-transformed posts plus a separately returned pinned post), and the 100%-covered schema handles the 11 parameters. Pagination defaults and sort ordering are not addressed, but the core behavior an agent needs is present.

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 11 parameters are documented in the schema and the baseline is 3. The description mentions 'page' and 'first page' but adds no syntax, format, or interaction detail (e.g., how search/search_in combine, per_page limits) beyond what the schema already states.

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 and resource ('Returns a page of posts the current user is allowed to read') with scope qualifier. However it does not distinguish itself from siblings like fc_get_feed or fc_list_spaces, so an agent gets a clear purpose but no sibling differentiation. The controller/route lines are metadata rather than purpose.

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?

The description says what it returns but never states when to use it versus alternatives such as fc_get_feed, fc_list_spaces, or fc_list_comments. No prerequisites, no exclusions, no routing guidance is provided.

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

Deploy Server

Other Tools