Skip to main content
Glama
Sign In

Nilyo

by com.nilyo
OverviewDiscussionsAdmin

Facebook / Messenger: Unfollow user

facebook_unfollow_user
Destructive

Unfollow 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_unfollow_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 declare destructiveHint=true, idempotentHint=false, openWorldHint=true, so the safety profile is partly covered. The description adds meaningful non-obvious behavior: this is an external action needing explicit user approval, and after an uncertain failure the agent must not retry but re-inspect state first — a direct, useful elaboration of the non-idempotent hint.

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?

Two tight sentences, zero filler, with the action statement front-loaded and the safety constraints immediately after. Every clause earns its place.

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?

No output schema exists, but for a binary follow-relationship mutation the description covers the essential risk profile and recovery behavior. Minor gap: it doesn't state what happens to followers/following counts or that the target must first be resolved via a sibling tool.

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 both user_id and account_id are well documented in the schema, including the numeric-ID restriction and the multi-account rule. The description adds nothing beyond this, so the schema-only baseline of 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 + resource: 'Unfollow the resolved Facebook person or Page,' which cleanly pairs against the sibling facebook_follow_user. The 'resolved' qualifier signals the target must come from a resolution step, though the description doesn't name facebook_resolve_person or facebook_list_friends as the source.

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 operational conditions ('preserve explicit user approval', 'inspect current state first') but no when-to-use-vs-alternatives guidance. It never says how this differs from facebook_remove_friend or when unfollowing is preferred over full removal, leaving the agent to infer that choice.

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