Skip to main content
Glama
Sign In

Nilyo

by com.nilyo
OverviewDiscussionsAdmin

Facebook / Messenger: List user posts

facebook_list_user_posts
Read-onlyIdempotent

List posts by a resolved person/Page, at most 3 per page; preserve cursor and author.

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_user_posts"
  }
}

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

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds that results are capped at 3 per page and that the cursor and author must be preserved, but the cursor semantics and the 3-item cap are already stated in the schema, so the net new behavioral information is thin.

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 front-loaded sentence with no filler and the scope constraint stated first. The trailing clause 'preserve cursor and author' is terse to the point of ambiguity, which is the only inefficiency.

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?

With no output schema, the description usefully signals that responses carry an author and a next cursor, which is the key shape information an agent needs for pagination. It says nothing about ordering, empty-result behavior, or how author identity is represented, so it is adequate rather than complete.

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 50%, and the description only gestures at user_id ('resolved person/Page') without explaining the 'me' default, the numeric-only pattern, or what account_id selects. The limit parameter is not mentioned at all in the description, leaving the missing schema descriptions uncompensated.

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 (List) and resource (posts) scoped to a 'resolved person/Page', which cleanly separates it from single-post siblings like facebook_get_post and from my-comment/reaction listers. It stops short of naming any sibling or the resolve_person prerequisite by name, so it is clear but not fully differentiated.

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 phrase 'by a resolved person/Page' implies the caller must resolve an identity first, but no explicit when-to-use or when-not-to-use guidance is given. Nothing tells the agent to prefer facebook_get_profile, facebook_list_user_posts' Instagram/LinkedIn analogues, or when to stop paging.

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