Skip to main content
Glama
Sign In

Nilyo

by com.nilyo
OverviewDiscussionsAdmin

Facebook / Messenger: List my comments

facebook_list_my_comments
Read-onlyIdempotent

Read your own or an activated Page's comment activity log, not arbitrary users' private activity.

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": {
      "user_id": "<user_id>"
    },
    "name": "facebook_list_my_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNoOpaque next_cursor from the previous page of this same account, identity and resource. No offset pagination.
user_idYesme
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description's scope restriction is the only real addition. It says nothing about ordering, page size, or what a 'comment activity log' actually itemises, and there is no output schema to fall back on.

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?

A single compact sentence with the scope constraint front-loaded and no filler. It is efficient, though so terse that the concision shades into under-specification for a 4-parameter tool.

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

Completeness3/5

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

With no output schema, the description should convey what the log contains (comments authored by me vs. comments on my content) and that results are cursor-paginated with a cap of 25. Neither is present, so an agent can invoke it but cannot predict the result set or pagination behaviour.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50% and the description adds no parameter meaning at all: it never mentions user_id='me', account_id selection, the 1-25 limit cap, or the opaque cursor. The half-documented parameters and the undocumented 'limit' leave the description doing nothing to compensate.

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 and resource ('Read ... comment activity log') plus the permitted subject scope ('your own or an activated Page'). It does not name the closest siblings (facebook_list_post_comments, facebook_list_comment_replies), so an agent still has to infer the boundary from the name alone.

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?

The clause 'not arbitrary users' private activity' functions as an exclusion, which is useful guidance, but no alternative tool is named and no positive trigger is given beyond the implicit 'I want my own comment activity'. The agent must map that to the sibling set on its own.

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