Skip to main content
Glama

fc_list_spaces

List and filter FluentCommunity spaces by status, type, privacy settings, or search terms to manage community content organization.

Instructions

List all spaces in FluentCommunity

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by status
typeNoFilter by space type
privacyNoFilter by privacy setting
limitNoNumber of spaces to return
searchNoSearch term

Implementation Reference

  • Handler function that executes the fc_list_spaces tool logic by constructing parameters and making a WordPress API request to fetch spaces.
    fc_list_spaces: async (args: any) => {
      try {
        const params: any = { per_page: args.limit || 20 };
        
        if (args.status) params.status = args.status;
        if (args.privacy) params.privacy = args.privacy;
        if (args.search) params.search = args.search;
        
        const response = await makeWordPressRequest('GET', 'fc-manager/v1/spaces', 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 defining parameters for the fc_list_spaces tool: status, privacy, limit, search.
    const listSpacesSchema = z.object({
      status: z.enum(['active', 'inactive', 'archived']).optional().describe('Filter by status'),
      privacy: z.enum(['public', 'private']).optional().describe('Filter by privacy setting'),
      limit: z.number().optional().default(20).describe('Number of spaces to return'),
      search: z.string().optional().describe('Search term')
    });
  • Registration of the fc_list_spaces tool in the fluentCommunityTools array, specifying name, description, and input schema.
    {
      name: 'fc_list_spaces',
      description: 'List all spaces in FluentCommunity',
      inputSchema: { type: 'object', properties: listSpacesSchema.shape }
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It doesn't indicate whether this is a read-only operation, what authentication might be required, how results are paginated (beyond the 'limit' parameter), what format the output takes, or any rate limits. The description only states what the tool does at the most basic level without behavioral context.

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 gets straight to the point with zero wasted words. It's appropriately sized for a list operation and front-loads the essential information. Every word earns its place in this minimal but complete statement of purpose.

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 that this is a list operation with 5 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't address what the output looks like, how pagination works beyond the 'limit' parameter, authentication requirements, or error conditions. For a tool with multiple filtering options and no structured output documentation, the description should provide more context about the operation's behavior and results.

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?

The input schema has 100% description coverage, with all 5 parameters clearly documented in the schema itself. The description adds no additional parameter information beyond what's already in the schema. According to the scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description, which applies here.

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 the verb ('List') and resource ('all spaces in FluentCommunity'), making the purpose immediately understandable. It distinguishes this tool from other list operations like fc_list_posts or fc_list_comments by specifying the resource type. However, it doesn't explicitly differentiate from fc_get_space (which retrieves a single space) or fc_search_content (which might also find spaces), so it's not a perfect 5.

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. It doesn't mention when to prefer fc_get_space for single-space retrieval, fc_search_content for broader searches, or fc_list_space_members for related data. There's also no information about prerequisites, permissions, or typical use cases beyond the basic action.

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