Skip to main content
Glama
Sign In

Nilyo

by com.nilyo
OverviewDiscussionsAdmin

Facebook / Messenger: Create post

facebook_create_post
Destructive

Publish as the explicitly selected owner or activated Page. Text can mention @. Photos OR one video; a share uses quoted_post_id without attachments. Visibility is public or friends. 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": {
      "text": "<text>",
      "post_as": "<post_as>"
    },
    "name": "facebook_create_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
post_asYesExplicit publishing identity: me or an activated administered Page ID from facebook_list_inboxes -> page_id, verified in Hosted Auth. A Page's messaging id and profile_id can differ. Never infer one from the other; reconnect the same account to activate Pages.
can_readNo
account_idNoOwned Facebook unipile_account_id from list_connected_accounts. Not a Facebook person or Page ID. Required when several Facebook accounts exist.
attachmentsNo
quoted_post_idNoFull Facebook post.id (<author_id>_<post_id>) from facebook_list_user_posts or facebook_get_post. Not a URL, text or author ID alone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare a non-idempotent, open-world, destructive write. The description adds meaningful behavior beyond them: explicit user approval is required for this external action, retries after uncertain failure are forbidden, current state should be inspected first, and content-type exclusivity rules apply. It stops short of auth/rate-limit details, so not a full 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?

Five short sentences, front-loaded with the publishing identity and followed by content, visibility, and safety constraints. Every sentence contributes a distinct operational rule with no filler.

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 6-parameter mutation tool with no output schema and moderate schema coverage, the description covers identity selection, mention syntax, attachment/share mutual exclusivity, visibility, and failure handling. Minor gaps remain around account_id selection logic, but the safety-critical behavior is complete.

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

Parameters4/5

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

With 50% schema coverage, the description compensates by explaining that text may contain @<resolved profile ID or vanity>, that attachments are photos OR one video, that a share uses quoted_post_id without attachments, and that visibility is public or friends. These are constraints not conveyed by the schema alone.

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 ('Publish') and resource (a Facebook post) and clarifies the publishing identity (self or activated Page). It is distinguishable from facebook_update_post/facebook_delete_post by implication, but it does not name sibling alternatives 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?

The description gives operating constraints (preserve user approval, never retry after uncertain failure, inspect state first) but does not say when to choose this tool over siblings such as social_create_post or facebook_update_post. Usage is implied through the publication framing rather than explicitly routed.

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