Skip to main content
Glama

fc_search_content

Search across FluentCommunity posts, comments, spaces, and users to find specific content using targeted queries and filters.

Instructions

Search across all FluentCommunity content (posts, comments, spaces)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query
content_typeNoType of content to searchall
space_idNoLimit search to specific space
limitNoNumber of results to return

Implementation Reference

  • Handler function for fc_search_content tool that performs a search query on FluentCommunity content via WordPress API.
    fc_search_content: async (args: any) => {
      try {
        const params: any = {
          query: args.query,
          content_type: args.content_type || 'all',
          per_page: args.limit || 20,
        };
        
        if (args.space_id) params.space_id = args.space_id;
        
        const response = await makeWordPressRequest('GET', 'fc-manager/v1/search', 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 schema defining input parameters for the fc_search_content tool.
    const searchContentSchema = z.object({
      query: z.string().describe('Search query'),
      content_type: z.enum(['all', 'posts', 'comments', 'spaces']).optional().default('all').describe('Type of content to search'),
      space_id: z.number().optional().describe('Limit search to specific space'),
      limit: z.number().optional().default(20).describe('Number of results to return')
    });
  • Registration of the fc_search_content tool in the fluentCommunityTools array.
    {
      name: 'fc_search_content',
      description: 'Search across all FluentCommunity content (posts, comments, spaces)',
      inputSchema: { type: 'object', properties: searchContentSchema.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. It mentions the scope ('across all FluentCommunity content') but lacks details on permissions, rate limits, pagination, or output format. For a search tool with 4 parameters and no output schema, this is a significant gap in transparency.

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 with zero waste—it directly states the tool's function and scope. It is front-loaded and appropriately sized, making it easy to parse without unnecessary elaboration.

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 tool's complexity (search across multiple content types), lack of annotations, and no output schema, the description is incomplete. It fails to address key behavioral aspects like result formatting, error handling, or authentication needs, leaving gaps for effective agent 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 input schema fully documents all parameters. The description adds no additional meaning beyond implying a broad search scope, which is already suggested by the schema's 'content_type' enum. Baseline score of 3 is appropriate as the schema handles parameter semantics adequately.

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 ('Search') and resource ('FluentCommunity content') with specific content types listed (posts, comments, spaces). It distinguishes itself from siblings like fc_list_posts or fc_list_spaces by emphasizing cross-content search, though it doesn't explicitly name alternatives. The purpose is specific and actionable.

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 like fc_list_posts or fc_list_spaces, nor does it mention prerequisites or exclusions. It states what the tool does but offers no context for selection among sibling tools, leaving usage decisions ambiguous.

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