Skip to main content
Glama

fc_get_post

Retrieve specific community post details by ID to access complete content, author information, and engagement metrics for content management.

Instructions

Get a specific post by ID with all details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
post_idYesThe ID of the post to retrieve

Implementation Reference

  • The async handler function that implements the core logic of fc_get_post by making a GET request to the WordPress API endpoint fc-manager/v1/posts/{post_id} and returning the post data or error.
    fc_get_post: async (args: any) => {
      try {
        const response = await makeWordPressRequest('GET', `fc-manager/v1/posts/${args.post_id}`);
        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 the input validation for the fc_get_post tool, requiring a numeric post_id parameter.
    const getPostSchema = z.object({
      post_id: z.number().describe('The ID of the post to retrieve')
    });
  • Registers the fc_get_post tool metadata (name, description, input schema) in the fluentCommunityTools export array.
    {
      name: 'fc_get_post',
      description: 'Get a specific FluentCommunity post by ID with all details',
      inputSchema: { type: 'object', properties: getPostSchema.shape }
    },
  • Top-level aggregation of all tools including fluentCommunityTools (which contains fc_get_post) into the allTools export.
    ...fluentCommunityTools,       // 21 tools (FluentCommunity spaces, posts, members)
  • Top-level aggregation of all handlers including fluentCommunityHandlers (which contains fc_get_post handler) into the toolHandlers export.
    ...fluentCommunityHandlers,
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 states the tool retrieves a post with all details, implying a read-only operation, but doesn't mention potential behaviors like error handling for invalid IDs, authentication requirements, rate limits, or response format. This leaves significant gaps in understanding how the tool behaves in practice.

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 front-loads the core purpose without unnecessary words. It directly communicates the action and key detail ('by ID with all details'), making it highly concise and well-structured for quick comprehension.

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?

For a tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'all details' includes in the return value, error scenarios, or how it differs from sibling retrieval tools. Given the complexity of a read operation in a system with multiple post-related tools, more context is needed to guide 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?

The input schema has 100% description coverage, with the 'post_id' parameter clearly documented as 'The ID of the post to retrieve'. The description adds no additional semantic context beyond this, such as ID format examples or constraints. Given the high schema coverage, a baseline score of 3 is appropriate as the schema handles the parameter documentation 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 ('Get') and resource ('a specific post by ID with all details'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'fc_list_posts' or 'fc_search_content' that also retrieve posts, which prevents a perfect score.

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' for multiple posts or 'fc_search_content' for broader searches. It lacks any context about prerequisites, error conditions, or typical use cases, leaving the agent with minimal usage direction.

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