Skip to main content
Glama

fc_update_post

Modify existing community posts by updating content, status, privacy settings, or metadata to maintain current and relevant discussions.

Instructions

Update an existing post in FluentCommunity

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
post_idYesThe ID of the post to update
titleNoPost title
messageNoPost content/message
message_renderedNoRendered HTML version of the message
typeNoPost type
statusNoPost status
privacyNoPost privacy setting
featured_imageNoURL of the featured image
metaNoAdditional metadata as JSON object

Implementation Reference

  • The main handler function for the 'fc_update_post' tool. It extracts post_id and update data from args, makes a POST request to the WordPress API endpoint 'fc-manager/v1/posts/{post_id}', and returns the response or error.
    fc_update_post: async (args: any) => {
      try {
        const { post_id, ...updateData } = args;
        const response = await makeWordPressRequest('POST', `fc-manager/v1/posts/${post_id}`, updateData);
        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_update_post' tool, including post_id (required), and optional fields like title, message, status, and privacy.
    const updatePostSchema = z.object({
      post_id: z.number().describe('The ID of the post to update'),
      title: z.string().optional().describe('Post title'),
      message: z.string().optional().describe('Post content/message'),
      status: z.enum(['published', 'draft', 'pending', 'archived']).optional().describe('Post status'),
      privacy: z.enum(['public', 'private', 'friends']).optional().describe('Post privacy setting')
    });
  • Tool registration in the fluentCommunityTools array, specifying the name 'fc_update_post', description, and referencing the updatePostSchema for input validation. This array is later spread into the main allTools export in src/tools/index.ts.
    {
      name: 'fc_update_post',
      description: 'Update an existing FluentCommunity post',
      inputSchema: { type: 'object', properties: updatePostSchema.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 'Update an existing post,' which implies a mutation operation, but does not disclose any behavioral traits such as required permissions, whether changes are reversible, rate limits, or what happens to unspecified fields (e.g., if they remain unchanged or are reset). This leaves significant gaps for an agent to understand the tool's behavior.

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, concise sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and efficiently communicates the core functionality, making it easy for an agent to parse quickly. There is no wasted verbiage or redundant information.

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 of a mutation tool with 9 parameters, no annotations, and no output schema, the description is incomplete. It lacks crucial context such as error conditions, response format, side effects, or how partial updates are handled. For a tool that modifies data, this minimal description does not provide enough information for an agent to use it effectively without additional assumptions.

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 clear documentation for all 9 parameters, including enums for status and privacy. The description adds no additional semantic information beyond what the schema provides, such as explaining parameter interactions or default behaviors. With high schema coverage, the baseline score of 3 is appropriate, as the description does not compensate but also does not detract.

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 action ('Update') and resource ('an existing post in FluentCommunity'), which is specific and unambiguous. However, it does not differentiate this tool from sibling tools like fc_bulk_update_posts or fc_update_comment, which would require mentioning it updates a single post by ID rather than multiple posts or other entities.

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 specify when to choose fc_update_post over fc_bulk_update_posts for multiple updates, or when to use it after fc_create_post for modifications. There is no mention of prerequisites, such as needing an existing post ID, which is implied but not explicitly stated in the description.

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