Skip to main content
Glama

fc_list_space_members

View and filter members in a FluentCommunity space by status to manage community participation and monitor user activity.

Instructions

List members of a specific space

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesThe space ID to list members from
statusNoFilter by member status
limitNoNumber of members to return

Implementation Reference

  • Handler function for fc_list_space_members tool. Makes a GET request to the WordPress REST API endpoint fc-manager/v1/spaces/{space_id}/members with optional parameters for status and limit, returns JSON response or error.
    fc_list_space_members: async (args: any) => {
      try {
        const params: any = {
          per_page: args.limit || 50,
        };
        
        if (args.status) params.status = args.status;
        
        const response = await makeWordPressRequest('GET', `fc-manager/v1/spaces/${args.space_id}/members`, params);
        return { toolResult: { content: [{ type: 'text', text: JSON.stringify(response, null, 2) }] } };
      } catch (error: any) {
        return { toolResult: { isError: true, content: [{ type: 'text', text: `Error: ${error.message}` }] } };
      }
    },
  • Zod input schema for fc_list_space_members tool defining parameters: space_id (required), status (optional enum), limit (optional number).
    const listSpaceMembersSchema = z.object({
      space_id: z.number().describe('The space ID to list members from'),
      status: z.enum(['active', 'pending', 'banned']).optional().describe('Filter by member status'),
      limit: z.number().optional().default(50).describe('Number of members to return')
    });
  • Registration of fc_list_space_members tool in the fluentCommunityTools array, including name, description, and reference to the input schema.
    {
      name: 'fc_list_space_members',
      description: 'List members of a specific FluentCommunity space',
      inputSchema: { type: 'object', properties: listSpaceMembersSchema.shape }
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('List members') but does not describe any behavioral traits such as pagination (implied by 'limit' parameter but not explained), rate limits, authentication requirements, or what the output format looks like (e.g., list of user objects). This leaves significant gaps for a tool with no annotations or output schema.

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 a single, efficient sentence that is front-loaded with the core purpose. There is no wasted verbiage or redundancy, making it easy to parse quickly. Every word earns its place by directly conveying the tool's function.

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

Completeness2/5

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

Given the complexity (a read operation with filtering and pagination), lack of annotations, and no output schema, the description is incomplete. It does not address key contextual aspects like what the output contains (e.g., member details), how pagination works beyond the 'limit' parameter, or error conditions. This leaves the agent under-informed for effective use.

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 the schema already documents all parameters ('space_id', 'status', 'limit') with descriptions and enums. The description adds no additional meaning beyond what the schema provides, such as explaining how 'status' filtering works in practice or default behaviors. Baseline 3 is appropriate when the schema does the heavy lifting.

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 'List members of a specific space' clearly states the verb ('List') and resource ('members of a specific space'), making the purpose immediately understandable. However, it does not explicitly differentiate from sibling tools like 'fc_get_space' (which retrieves space metadata) or 'fc_list_spaces' (which lists spaces themselves), though the distinction is reasonably implied by the resource focus.

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 provides no guidance on when to use this tool versus alternatives. For example, it does not mention that 'fc_get_space' might provide member counts or basic info, or that 'fc_remove_space_member' is for deletion, leaving the agent to infer usage from tool names alone. There is no explicit when/when-not or alternative tool references.

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/wplaunchify/fluent-community-mcp'

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