Skip to main content
Glama
Sign In

Nilyo

by com.nilyo
OverviewDiscussionsAdmin

Facebook / Messenger: Follow user

facebook_follow_user
Destructive

Follow the resolved Facebook person or Page. 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": {
      "user_id": "<user_id>"
    },
    "name": "facebook_follow_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesNumeric Facebook profile.id from facebook_get_profile, facebook_list_friends or facebook_list_contacts. Not a name, vanity URL, connection account_id or Page messaging ID.
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.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds genuine context those flags cannot: this is an external, user-visible action requiring explicit approval, and an uncertain failure must not be retried. It doesn't say whether the action is reversible via unfollow or what happens if already following, which keeps it short of a 5.

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?

Three short sentences with zero padding; the action is front-loaded and the safety constraints follow in order of importance. Every clause carries distinct information.

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 write tool with no output schema, the definition covers approval, failure handling, and state inspection, and the schema fully documents both parameters. What's missing is outcome information an agent would want: whether following an already-followed target errors, and how to undo it.

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 100% and the schema descriptions are unusually thorough (numeric profile.id only, not a name/vanity URL/account_id, plus when account_id is required). The description adds only the 'resolved' framing, which is a marginal reinforcement rather than new meaning, so baseline 3 applies.

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 (Follow) and resource (resolved Facebook person or Page), and the word 'resolved' signals that an ID must be obtained first, which separates it from the resolve/list siblings. It does not explicitly name facebook_unfollow_user as the inverse operation, so sibling differentiation is implied rather than spelled out.

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?

Gives real operational guidance: require explicit user approval, do not retry after an uncertain failure, inspect state first. However, it never states when to prefer this tool over alternatives (unfollow, resolve_person, sending a friend request), nor that the ID must come from facebook_get_profile/list_friends before calling.

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