Skip to main content
Glama
Sign In

Nilyo

by com.nilyo
OverviewDiscussionsAdmin

Facebook / Messenger: Update comment

facebook_update_comment
Destructive

Edit the selected Facebook comment's text. 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>",
      "comment_id": "<comment_id>",
      "text": "<text>"
    },
    "name": "facebook_update_comment"
  }
}

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.
comment_idYesNumeric comment.id from facebook_list_post_comments or facebook_list_comment_replies, paired with that post_id. Not comment text or post ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, openWorldHint=true, idempotentHint=false, so safety profile is partly covered. The description adds genuinely new operational context: an external action requiring user approval and a no-retry policy on uncertain failures, which is valuable and not derivable from annotations.

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 with zero padding, front-loading the action before the safety caveats. The 'External action:' label is slightly cryptic but overall tight.

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 destructive, non-idempotent mutation with no output schema, the description supplies the key behavioural guardrails (approval, no retry, inspect first). It does not mention what is returned after a successful edit or whether edit history is retained, but core call-safety needs are met.

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 75% and already documents post_id, comment_id and account_id with precise formats and provenance. The description only obliquely covers the undocumented 'text' parameter ('comment's text') and adds no format or length detail beyond the schema.

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 ('edit') and resource ('the selected Facebook comment's text'), which is clearly distinct from create/delete/reply comment siblings. It stops short of naming the alternatives (e.g. facebook_delete_comment, facebook_reply_to_comment) explicitly.

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

Usage Guidelines3/5

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

'Preserve explicit user approval' implies a precondition for use, and 'inspect current state first' gives recovery guidance, but there is no explicit statement of when to choose this over facebook_update_post or a reply/delete tool.

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