Skip to main content
Glama
Sign In

Nilyo

by com.nilyo
OverviewDiscussionsAdmin

Facebook / Messenger: Update post

facebook_update_post
Destructive

Edit post text only, preserving media and audience. External action: preserve explicit user approval. Never retry after an uncertain failure; inspect current state first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "post_id": "<post_id>",
      "text": "<text>"
    },
    "name": "facebook_update_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
post_idYesFull Facebook post.id (<author_id>_<post_id>) from facebook_list_user_posts or facebook_get_post. Not a URL, text or author ID alone.
account_idNoOwned Facebook unipile_account_id from list_connected_accounts. Not a Facebook person or Page ID. Required when several Facebook accounts exist.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=false and openWorldHint=true. The description adds real value beyond them: the destructive scope is bounded to text, an explicit human-approval requirement is stated for this external action, and a no-retry-after-uncertain-failure policy with a state-inspection workaround is given.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the operation scope before the safety rules. 'External action: preserve explicit user approval' is slightly telegraphic but not wasteful.

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

Completeness4/5

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

For a 3-parameter mutation with no output schema, the description covers mutation scope, approval requirements, and failure handling. It doesn't say what a successful update returns, but with annotations carrying the safety profile that gap is minor.

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 coverage is 67% and the two complex parameters (post_id format, account_id disambiguation) are already documented in the schema. The description adds only the implicit constraint that 'text' is the sole mutable field, with no format or length guidance beyond that.

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?

States a specific verb+resource with scope: 'Edit post text only, preserving media and audience.' This separates it from facebook_delete_post, facebook_create_post and facebook_update_comment without naming them, though it doesn't explicitly call out those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'preserving media and audience' signals when this is the right tool (text-only edits) and when it is not (media or audience changes). 'inspect current state first' gives a concrete pre-call step, but no alternative tool is named for cases needing media/audience changes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nilyo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources