Skip to main content
Glama

Server Details

Your own LinkedIn, WhatsApp, Instagram, Telegram, Email and Calendar accounts, usable from any agent

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
nilyo-com/nilyo-mcp
GitHub Stars
0
Server Listing
Nilyo
ChatGPT
–
Claude
–

TDQS

C2.8/5.0

Scored across 233 tools

Disambiguation1/5

The set has multiple overlapping layers for the same actions: generic social_delete_comment/social_update_post coexist with facebook_*, linkedin_* and instagram_* equivalents; messaging_send_message/message_* overlap with whatsapp_send_message, linkedin_send_message, instagram_send_message and facebook chat tools; resolver/listing tools also duplicate each other (email_list_folders vs email_resolve_folder, message_resolve_chat vs messaging_list_chats). With 233 tools, an agent cannot reliably tell which family is authoritative for a given provider/action.

Naming Consistency2/5

Names are all snake_case, but the prefix conventions are inconsistent: message_, messaging_ and chat_ coexist; social_ generic tools coexist with provider-specific facebook_/linkedin_/instagram_ tools; account_, team_, webhook_, feedback_ and agent_ add more families. The result is readable in isolation but not predictable as a set.

Tool Count1/5

233 tools is far beyond a well-scoped set and reflects an all-in-one platform exposing many overlapping provider-specific and generic layers. The count makes selection, discovery and maintenance costly; many tools appear to earn their place only within a particular provider family, not as a coherent whole.

Completeness4/5

The surface covers a very broad domain: email, calendar, messaging, social posting/comments/reactions, recruiting, billing, account connections and webhooks, with mostly complete CRUD/lifecycle operations. Gaps remain such as Instagram Story listing, Facebook pins/labels, and LinkedIn company-follow invitation state lookup, but these are mostly edge-case limitations rather than core workflow dead ends.

Publisher details

Operator
Nilyo · Publisher source
Vendor relationship
First-party · Publisher source
Privacy policy
Not provided
Restrictions
Requires a Nilyo account (created during the OAuth flow, 7-day free trial, no card; paid plans afterwards at https://nilyo.com/pricing). Users connect their own provider accounts (LinkedIn, WhatsApp, Instagram, Telegram, Gmail, Outlook, IMAP, calendars). No admin approval, no custom OAuth app to create, no regional limit beyond ChatGPT/Claude availability.

Available Tools

233 tools
account_change_planAccount: Change planA
Destructive
Inspect

Change the user's plan (Personal, Personal Plus, Team) or billing interval. During the trial the choice is free and applies immediately. With an active Stripe subscription the change is prorated immediately on the saved payment method: FIRST call without confirm to get the price and the explanation (and a one-click Stripe confirmation link), show them to the user, and only call again with confirm=true after explicit approval. Use when a second account of a provider needs Personal Plus, when the user wants Team for colleagues, or asks to switch monthly/annual.

Inputs: plan (required), confirm, interval, organization_name.

account_connectAccount: ConnectAInspect

Get a secure connection (or reconnection) link for one of the user's provider accounts: LinkedIn, WhatsApp, Instagram, Facebook/Messenger (including selected Pages), Telegram, Google/Gmail, Microsoft/Outlook or generic IMAP email. Use when the user asks to connect/add/reconnect an account, or after a connect_account/reconnect_account result. Pass account_id only to re-authenticate an existing account (from list_connected_accounts), including a healthy Facebook account needing additional Pages or a healthy LinkedIn account needing Company Pages or a different premium product. Facebook Hosted Auth offers Messenger and administered Pages for explicit selection. LinkedIn Hosted Auth offers Classic, Company Pages, Sales Navigator and Recruiter when available; the user must select them. Sales Navigator and Recruiter cannot be active together on one connection. Afterward use linkedin_list_managed_company_pages and linkedin_list_inboxes to inspect accessible pages/products. WhatsApp and Telegram also support QR connection through whatsapp_connect / telegram_connect; account_connect returns the browser link. Never ask the user for provider passwords; the link opens the provider's own authentication.

Inputs: provider (required), account_id.

account_connection_statusAccount: Connection statusA
Destructive
Inspect

Check an in-conversation WhatsApp/Telegram connection started with whatsapp_connect or telegram_connect. Returns pending (with the current QR code image or pairing code, refreshed when it changed), connected, expired or failed. Poll every 10-20 seconds until the status is connected, then retry the user's original request. Omit intent_id to check the most recent attempt. This also expires stale connection intents and may create a Hosted Auth recovery link for a finished attempt.

Inputs: intent_id.

account_get_subscriptionAccount: Get subscriptionAInspect

Show the authenticated Nilyo user's login email, plan, trial/subscription status, account limits, team seats and members, plus the available billing actions (subscribe, upgrade, add seats, invite). Use to verify which Nilyo login the agent is connected to, when the user asks about their plan, trial, price, seats, team, why an action is blocked, or before proposing an upgrade. For clients that allow billing links, this may create a Stripe portal session for a paid subscription. ChatGPT receives only current account and entitlement status. Never exposes payment details.

Inputs: no named parameters.

account_list_attentionAccount: List attentionA
Read-onlyIdempotent
Inspect

List the user's connected accounts that currently need re-authentication (status disconnected) so the agent can proactively offer to reconnect them before a request fails. Returns an empty list when everything is healthy.

Inputs: no named parameters.

account_start_subscriptionAccount: Start subscriptionAInspect

Return Stripe Checkout links (one-click hosted payment, no need to visit the website) to start or restore the paid subscription when the user is on trial, the trial expired or the subscription lapsed. Use after a subscribe result or when the user asks to subscribe/pay/upgrade before having a subscription. If the user already has an active Stripe subscription, use account_change_plan instead. Present monthly and annual options; default to the current plan unless the user chose another one.

Inputs: plan, interval.

agent_capability_guideGuide: Capability guideA
Read-onlyIdempotent
Inspect

Return Nilyo's agent workflow recipes and chaining rules. Use when you need to know how to turn a LinkedIn URL/name into a provider user ID, how to find a chat before replying, how to resolve LinkedIn search parameter IDs, or how to combine several account providers.

Inputs: workflow.

agent_id_guideGuide: ID guideA
Read-onlyIdempotent
Inspect

Return the authoritative Nilyo ID semantics guide. Use this when unsure whether a tool needs a LinkedIn system user ID, public identifier, request ID, post/comment/chat/message ID, inbox/contract ID, email/thread/folder/attachment ID, calendar/event ID or recruiting/list ID. The guide explains exactly which previous tool produces each ID and which lookalike values must NOT be passed.

Inputs: id_type.

calendar_cancel_eventCalendar: Cancel eventA
Destructive
Inspect

Cancel an event organized by the connected account and notify attendees. This differs from deleting an event only from the user's calendar; confirm the exact event before cancellation.

Inputs: event_id (required), calendar_id (required), comment, account_id.

calendar_create_calendarCalendar: Create calendarAInspect

Create a calendar in the selected Google or Microsoft account. Use only when the user explicitly asks for a new calendar, not merely an event.

Inputs: name (required), timezone, account_id, description, +1 more.

calendar_create_eventCalendar: Create eventA
Destructive
Inspect

Create an event in one resolved calendar. Require an explicit title, attendees array, start and end; preserve timezone and all-day semantics instead of guessing them.

Inputs: end (required), start (required), title (required), attendees (required), +12 more.

calendar_delete_calendarCalendar: Delete calendarA
Destructive
Inspect

Delete one exact calendar. This is destructive: resolve and confirm the calendar before deleting it; never infer calendar_id from its display name.

Inputs: calendar_id (required), account_id.

calendar_delete_eventCalendar: Delete eventA
Destructive
Inspect

Delete one resolved calendar event. Confirm the intended event and preserve its parent calendar_id; this removes it only from the connected account's calendar.

Inputs: event_id (required), calendar_id (required), account_id.

calendar_get_calendarCalendar: Get calendarA
Read-onlyIdempotent
Inspect

Read one calendar by exact provider ID, normally resolved with calendar_list_calendars. Google can also read accessible public calendars by ID; this lookup is not restricted to the private calendar list. Outlook stays account-bound. Calendar ID: Exact Google/Microsoft calendar id. Obtain with: calendar_list -> calendar.id Never pass: calendar display name.

Inputs: calendar_id (required), account_id.

calendar_get_eventCalendar: Get eventA
Read-onlyIdempotent
Inspect

Get one event using both its exact parent calendar_id and event_id. Never identify an event only by title or date. Google may read an accessible public calendar by ID even outside the private calendar list; Outlook stays account-bound.

Inputs: event_id (required), calendar_id (required), account_id.

calendar_list_calendarsCalendar: List calendarsA
Read-onlyIdempotent
Inspect

List calendars for the connected Google or Microsoft account. Use the returned calendar.id before listing, creating or updating events; never pass a calendar display name as calendar_id.

Inputs: limit, cursor, offset, account_id.

calendar_list_eventsCalendar: List eventsA
Read-onlyIdempotent
Inspect

List or search events inside one resolved calendar. Use this to obtain event.id before reading, updating or deleting an event. Google may read an accessible public calendar by ID even outside the private calendar list; Outlook stays account-bound.

Inputs: calendar_id (required), end, busy, limit, +14 more.

calendar_restore_eventCalendar: Restore eventA
Destructive
Inspect

Restore an event previously cancelled by the connected organizer. Available only for Google Calendar while Google still retains the cancelled event; report the provider error for Outlook without substituting another action.

Inputs: event_id (required), calendar_id (required), account_id.

calendar_rsvp_eventCalendar: Rsvp eventA
Destructive
Inspect

Accept, tentatively accept or decline an invitation for the connected account only. Resolve the event first; Outlook organizers cannot RSVP and declining can remove the event from their calendar.

Inputs: status (required), event_id (required), calendar_id (required), comment, +1 more.

calendar_update_calendarCalendar: Update calendarB
Destructive
Inspect

Update explicit fields on an existing calendar. Resolve calendar_id first and pass only changes requested by the user.

Inputs: calendar_id (required), name, timezone, account_id, +2 more.

calendar_update_eventCalendar: Update eventA
Destructive
Inspect

Update explicit fields on a resolved event. Keep event_id paired with the parent calendar_id and do not blindly retry after an ambiguous failure.

Inputs: event_id (required), calendar_id (required), end, body, +13 more.

chat_add_participantChat: Add participantA
Destructive
Inspect

Add an exact provider user to an exact group chat. Resolve chat_id independently from user_id. For LinkedIn user references, URL/name -> profile resolver -> profile.id. Chat ID: Exact provider chat/conversation ID. LinkedIn chat IDs may also be visible in /messaging/thread/{chat_id}/ URLs. Obtain with: provider list conversations/inbox chats -> chat.id Never pass: person name, user_id, message_id. LinkedIn system user ID: Stable LinkedIn user id, commonly ACo... for Classic profiles. Obtain with: linkedin_get_profile_from_url(profile_url) -> result.id; linkedin_get_profile(user_id_or_public_identifier) -> result.id; linkedin_search_people(...) -> selected result.id Never pass: full linkedin.com/in/... URL, person name, company ID.

Inputs: chat_id (required), user_id (required), account_id.

chat_deleteChat: DeleteA
Destructive
Inspect

Delete/remove one exact chat where supported. Resolve/verify chat_id first; destructive. Chat ID: Exact provider chat/conversation ID. LinkedIn chat IDs may also be visible in /messaging/thread/{chat_id}/ URLs. Obtain with: provider list conversations/inbox chats -> chat.id Never pass: person name, user_id, message_id.

Inputs: chat_id (required), account_id.

chat_list_participantsChat: List participantsA
Read-onlyIdempotent
Inspect

List members of an exact group/multi-party chat. Resolve chat_id first. Returned participant user IDs can be reused for membership operations; they are NOT chat IDs. Chat ID: Exact provider chat/conversation ID. LinkedIn chat IDs may also be visible in /messaging/thread/{chat_id}/ URLs. Obtain with: provider list conversations/inbox chats -> chat.id Never pass: person name, user_id, message_id.

Inputs: chat_id (required), account_id.

chat_remove_participantChat: Remove participantA
Destructive
Inspect

Remove an exact provider user from an exact group chat. Inspect participants first when identity is ambiguous. chat_id and user_id are separate. Chat ID: Exact provider chat/conversation ID. LinkedIn chat IDs may also be visible in /messaging/thread/{chat_id}/ URLs. Obtain with: provider list conversations/inbox chats -> chat.id Never pass: person name, user_id, message_id.

Inputs: chat_id (required), user_id (required), account_id.

chat_updateChat: UpdateB
Destructive
Inspect

Update mutable metadata of an exact chat. Resolve chat_id first; do not use person/user ID. Pass only fields explicitly requested. Chat ID: Exact provider chat/conversation ID. LinkedIn chat IDs may also be visible in /messaging/thread/{chat_id}/ URLs. Obtain with: provider list conversations/inbox chats -> chat.id Never pass: person name, user_id, message_id.

Inputs: chat_id (required), name, label, account_id, +4 more.

email_create_draftEmail: Create draftAInspect

Create an email draft without sending. If replying, first read the source email and use the provider-appropriate reply_to_message_id (IMAP may use RFC822 Message-ID).

Inputs: to (required), cc, bcc, html, +4 more.

email_create_folderEmail: Create folderBInspect

Create a mailbox folder/label. parent_id, when supplied, must be an exact existing folder ID resolved from email_list_folders; it is not a parent folder display name.

Inputs: name (required), parent_id, account_id.

email_delete_draftEmail: Delete draftA
Destructive
Inspect

Discard one exact draft. draft_id comes from draft list/create; destructive.

Inputs: draft_id (required), account_id.

email_delete_folderEmail: Delete folderA
Destructive
Inspect

Delete one exact mailbox folder/label. Resolve folder_id first and verify target; destructive. Mailbox folder/label ID: Exact Gmail label, Outlook folder or IMAP folder id. Obtain with: email_list_folders -> folder.id Never pass: human folder name such as Inbox when an ID is required.

Inputs: folder_id (required), account_id.

email_get_attachmentEmail: Get attachmentA
Read-onlyIdempotent
Inspect

Retrieve one exact attachment from Gmail, Outlook/Microsoft or IMAP. Required chain: resolve/list email -> email_id -> read email -> attachment.id -> retrieve. Filename is NOT attachment_id. Email provider ID: Exact email ID returned by Nilyo for the connected mailbox. On IMAP (and Exchange over IMAP) the ID encodes folder + UID: it CHANGES when the email is moved or a draft is updated; always reuse the id returned by the last operation. Obtain with: email_list_messages or email_list_folder_messages -> email.id; the id returned by email_move_or_label / email_update_draft after a change Never pass: RFC Message-ID unless a tool explicitly documents it, subject, an email_id captured before a move/update on IMAP. Attachment ID: Exact attachment id returned inside a specific email/message. Obtain with: read the parent email/message first -> attachment.id Never pass: filename, URL.

Inputs: email_id (required), attachment_id (required), account_id.

email_get_draftEmail: Get draftA
Read-onlyIdempotent
Inspect

Get one exact draft. draft_id must come from email_list_drafts or email_create_draft; never use subject/email_id.

Inputs: draft_id (required), account_id.

email_get_folderEmail: Get folderA
Read-onlyIdempotent
Inspect

Get one exact Gmail/Outlook/IMAP folder. Resolve folder name -> folder.id first. Mailbox folder/label ID: Exact Gmail label, Outlook folder or IMAP folder id. Obtain with: email_list_folders -> folder.id Never pass: human folder name such as Inbox when an ID is required.

Inputs: folder_id (required), account_id.

email_get_threadEmail: Get threadA
Read-onlyIdempotent
Inspect

Retrieve full email thread by exact thread_id. Obtain thread_id from email list/read response; do not substitute subject/email_id. Email thread ID: Exact thread/conversation id returned by the email provider when available. Obtain with: email list/read result -> thread_id Never pass: email_id unless equal according to returned data.

Inputs: thread_id (required), account_id.

email_list_contactsEmail: List contactsA
Read-onlyIdempotent
Inspect

List Gmail/Microsoft contacts to resolve a human recipient name to an email address before composing. Generic IMAP normally has no provider contact directory; use mailbox context instead.

Inputs: limit, cursor, account_id.

email_list_draftsEmail: List draftsA
Read-onlyIdempotent
Inspect

List email drafts. Returned draft.id is the draft_id for get/update/send/delete. draft_id is not email_id or subject.

Inputs: limit, cursor, any_email, account_id.

email_list_folder_messagesEmail: List folder messagesA
Read-onlyIdempotent
Inspect

List messages inside one exact folder. Especially for IMAP: list folders -> select folder.id -> list messages -> email.id -> read/action. Dates: after/before are ISO 8601 UTC datetimes (YYYY-MM-DDTHH:MM:SS.sssZ); for "today" use after=start of the user's day. Counting: an empty page is not "zero emails" unless no filter was applied; for totals use folder.total_count/unread_count from email_list_folders instead of listing. IMAP pages are capped at 50 live messages; keep limit small (20) to avoid runtime timeouts. Mailbox folder/label ID: Exact Gmail label, Outlook folder or IMAP folder id. Obtain with: email_list_folders -> folder.id Never pass: human folder name such as Inbox when an ID is required. Email provider ID: Exact email ID returned by Nilyo for the connected mailbox. On IMAP (and Exchange over IMAP) the ID encodes folder + UID: it CHANGES when the email is moved or a draft is updated; always reuse the id returned by the last operation. Obtain with: email_list_messages or email_list_folder_messages -> email.id; the id returned by email_move_or_label / email_update_draft after a change Never pass: RFC Message-ID unless a tool explicitly documents it, subject, an email_id captured before a move/update on IMAP.

Inputs: folder_id (required), to, from, after, +5 more.

email_list_foldersEmail: List foldersA
Read-onlyIdempotent
Inspect

List Gmail labels, Outlook folders or IMAP folders. Returned folder.id is required by folder-specific operations. For IMAP this is normally the first step before listing messages. Mailbox folder/label ID: Exact Gmail label, Outlook folder or IMAP folder id. Obtain with: email_list_folders -> folder.id Never pass: human folder name such as Inbox when an ID is required.

Inputs: limit, cursor, account_id.

email_list_messagesEmail: List messagesA
Read-onlyIdempotent
Inspect

List email messages from the user's connected Gmail, Microsoft/Outlook OR generic IMAP mailbox. Use for a requested mailbox listing or to obtain email context for a cross-channel task. Use to find email_id before opening a message. For totals use email_list_folders (folder.total_count); IMAP pages are capped at 50 and listed live, keep limit small (20).

Inputs: after, limit, before, cursor, +2 more.

email_mark_readEmail: Mark readB
Destructive
Inspect

Mark one exact email read. Resolve human email reference -> email_id first. Email provider ID: Exact email ID returned by Nilyo for the connected mailbox. On IMAP (and Exchange over IMAP) the ID encodes folder + UID: it CHANGES when the email is moved or a draft is updated; always reuse the id returned by the last operation. Obtain with: email_list_messages or email_list_folder_messages -> email.id; the id returned by email_move_or_label / email_update_draft after a change Never pass: RFC Message-ID unless a tool explicitly documents it, subject, an email_id captured before a move/update on IMAP.

Inputs: email_id (required), account_id.

email_mark_unreadEmail: Mark unreadB
Destructive
Inspect

Mark one exact email unread. Resolve email_id first. Email provider ID: Exact email ID returned by Nilyo for the connected mailbox. On IMAP (and Exchange over IMAP) the ID encodes folder + UID: it CHANGES when the email is moved or a draft is updated; always reuse the id returned by the last operation. Obtain with: email_list_messages or email_list_folder_messages -> email.id; the id returned by email_move_or_label / email_update_draft after a change Never pass: RFC Message-ID unless a tool explicitly documents it, subject, an email_id captured before a move/update on IMAP.

Inputs: email_id (required), account_id.

email_move_or_labelEmail: Move or labelA
Destructive
Inspect

Move/label one exact email. The result is the email after the change: on IMAP its id CHANGES (folder+UID), so reuse result.id for any follow-up. Resolve email_id independently, then resolve every human folder name to folder.id. Never put 'Inbox'/'Archive' strings in folders_ids unless the provider actually returned those strings as IDs. Email provider ID: Exact email ID returned by Nilyo for the connected mailbox. On IMAP (and Exchange over IMAP) the ID encodes folder + UID: it CHANGES when the email is moved or a draft is updated; always reuse the id returned by the last operation. Obtain with: email_list_messages or email_list_folder_messages -> email.id; the id returned by email_move_or_label / email_update_draft after a change Never pass: RFC Message-ID unless a tool explicitly documents it, subject, an email_id captured before a move/update on IMAP. Mailbox folder/label ID: Exact Gmail label, Outlook folder or IMAP folder id. Obtain with: email_list_folders -> folder.id Never pass: human folder name such as Inbox when an ID is required.

Inputs: email_id (required), folders_ids (required), specifics, account_id.

email_read_messageEmail: Read messageA
Read-onlyIdempotent
Inspect

Read a specific email including body/headers from Gmail, Microsoft/Outlook or IMAP. Use after email_list_messages and before a contextual reply or cross-channel decision.

Inputs: email_id (required), account_id.

email_resolve_folderEmail: Resolve folderA
Read-onlyIdempotent
Inspect

List mailbox folders/labels to map human names such as Inbox, Archive, Junk or a custom folder to exact folder_id before moving/labeling or listing folder messages. This is especially important for IMAP. Mailbox folder/label ID: Exact Gmail label, Outlook folder or IMAP folder id. Obtain with: email_list_folders -> folder.id Never pass: human folder name such as Inbox when an ID is required.

Inputs: limit, cursor, account_id.

email_resolve_messageEmail: Resolve messageA
Read-onlyIdempotent
Inspect

Search/list email candidates so a human reference such as sender, recipient, subject or date can be mapped to exact email_id before read/reply/trash/move/attachment operations. For generic IMAP, if account-wide listing is unavailable, use email_list_folders then email_list_folder_messages instead. Email provider ID: Exact email ID returned by Nilyo for the connected mailbox. On IMAP (and Exchange over IMAP) the ID encodes folder + UID: it CHANGES when the email is moved or a draft is updated; always reuse the id returned by the last operation. Obtain with: email_list_messages or email_list_folder_messages -> email.id; the id returned by email_move_or_label / email_update_draft after a change Never pass: RFC Message-ID unless a tool explicitly documents it, subject, an email_id captured before a move/update on IMAP. Email reply reference: For Gmail/Outlook normally use the provider email id. For generic IMAP, reply_to_message_id may be the RFC822 Message-ID returned in the email data. Obtain with: email_read_message -> inspect id and provider/RFC Message-ID fields Never pass: subject, sender email address. Email thread ID: Exact thread/conversation id returned by the email provider when available. Obtain with: email list/read result -> thread_id Never pass: email_id unless equal according to returned data.

Inputs: to, from, after, limit, +4 more.

email_sendEmail: SendA
Destructive
Inspect

Send or reply to an email from the user's connected Gmail, Microsoft/Outlook or IMAP account. Use reply_to_message_id for a true reply when available. Only send after the user has clearly requested/approved the final recipients and content.

Inputs: to (required), cc, bcc, html, +4 more.

email_send_draftEmail: Send draftA
Destructive
Inspect

Send one exact existing draft. Resolve draft_id and inspect final recipients/content first when not already explicitly approved; this creates a real external send.

Inputs: draft_id (required), account_id.

email_trashEmail: TrashB
Destructive
Inspect

Trash one exact email. Resolve email_id first; destructive mailbox action. Email provider ID: Exact email ID returned by Nilyo for the connected mailbox. On IMAP (and Exchange over IMAP) the ID encodes folder + UID: it CHANGES when the email is moved or a draft is updated; always reuse the id returned by the last operation. Obtain with: email_list_messages or email_list_folder_messages -> email.id; the id returned by email_move_or_label / email_update_draft after a change Never pass: RFC Message-ID unless a tool explicitly documents it, subject, an email_id captured before a move/update on IMAP.

Inputs: email_id (required), account_id.

email_update_draftEmail: Update draftA
Destructive
Inspect

Update an exact existing draft. On IMAP the updated draft gets a NEW draft.id (returned in the result); use it for email_send_draft. Without sending. Resolve/read draft first when preserving recipients/content matters.

Inputs: draft_id (required), cc, to, bcc, +5 more.

email_update_folderEmail: Update folderB
Destructive
Inspect

Rename/move one existing folder. Resolve folder_id first; parent_id is also an exact folder ID when supplied. Mailbox folder/label ID: Exact Gmail label, Outlook folder or IMAP folder id. Obtain with: email_list_folders -> folder.id Never pass: human folder name such as Inbox when an ID is required.

Inputs: folder_id (required), name, parent_id, account_id.

facebook_accept_friend_requestFacebook / Messenger: Accept friend requestA
Destructive
Inspect

Accept a received request. Use request.id from facebook_list_friend_requests, which for Facebook equals the person's ID. External action: preserve explicit user approval. Never retry after an uncertain failure; inspect current state first.

Inputs: request_id (required), account_id.

facebook_accept_message_requestFacebook / Messenger: Accept message requestA
Destructive
Inspect

Accept the selected message request in its original inbox. External action: preserve explicit user approval. Never retry after an uncertain failure; inspect current state first.

Inputs: chat_id (required), inbox_id (required), account_id.

facebook_add_comment_reactionFacebook / Messenger: Add comment reactionA
Destructive
Inspect

React to the selected comment as the explicit identity. External action: preserve explicit user approval. Never retry after an uncertain failure; inspect current state first.

Inputs: post_id (required), react_as (required), reaction (required), comment_id (required), +1 more.

facebook_add_post_reactionFacebook / Messenger: Add post reactionA
Destructive
Inspect

React to this post as the explicitly selected identity. External action: preserve explicit user approval. Never retry after an uncertain failure; inspect current state first.

Inputs: post_id (required), react_as (required), reaction (required), account_id.

facebook_cancel_friend_requestFacebook / Messenger: Cancel friend requestA
Destructive
Inspect

Cancel/reject the selected sent/received friend request. External action: preserve explicit user approval. Never retry after an uncertain failure; inspect current state first.

Inputs: request_id (required), account_id.

facebook_comment_on_postFacebook / Messenger: Comment on postA
Destructive
Inspect

Comment as the explicitly selected identity, with at most one image. External action: preserve explicit user approval. Never retry after an uncertain failure; inspect current state first.

Inputs: text (required), post_id (required), comment_as (required), account_id, +1 more.

facebook_create_postFacebook / Messenger: Create postA
Destructive
Inspect

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.

Inputs: text (required), post_as (required), can_read, account_id, +2 more.

facebook_delete_commentFacebook / Messenger: Delete commentA
Destructive
Inspect

Delete the selected comment from this post. External action: preserve explicit user approval. Never retry after an uncertain failure; inspect current state first.

Inputs: post_id (required), comment_id (required), account_id.

facebook_delete_postFacebook / Messenger: Delete postA
Destructive
Inspect

Delete the resolved Facebook post. External action: preserve explicit user approval. Never retry after an uncertain failure; inspect current state first.

Inputs: post_id (required), account_id.

facebook_follow_userFacebook / Messenger: Follow userA
Destructive
Inspect

Follow the resolved Facebook person or Page. External action: preserve explicit user approval. Never retry after an uncertain failure; inspect current state first.

Inputs: user_id (required), account_id.

facebook_get_account_statusFacebook / Messenger: Get account statusA
Read-onlyIdempotent
Inspect

Inspect current Facebook product statuses, including each activated Page. partial/degraded means some products work and others need attention; reconnect the SAME account to review Page activation. Pages are products, not extra billable accounts. Only status/name metadata is returned.

Inputs: account_id.

facebook_get_chatFacebook / Messenger: Get chatA
Read-onlyIdempotent
Inspect

Read the exact personal or Page conversation selected from its inbox. Keep the full Page-prefixed chat ID.

Inputs: chat_id (required), account_id.

facebook_get_chat_pictureFacebook / Messenger: Get chat pictureA
Read-onlyIdempotent
Inspect

Download the current picture of the exact personal/Page chat selected from its inbox.

Inputs: chat_id (required), account_id.

facebook_get_my_profileFacebook / Messenger: Get my profileB
Read-onlyIdempotent
Inspect

Read the Facebook account owner's profile and stable numeric ID.

Inputs: account_id.

facebook_get_postFacebook / Messenger: Get postC
Read-onlyIdempotent
Inspect

Read the full resolved Facebook post ID, including author prefix.

Inputs: post_id (required), account_id.

facebook_get_profileFacebook / Messenger: Get profileA
Read-onlyIdempotent
Inspect

Read a known Facebook profile. Numeric ID or numeric profile.php?id= URL only; vanity names are not a universal profile search. Resolve a name from friends/contacts and disambiguate, without sending a message.

Inputs: user_id_or_url (required), account_id.

facebook_get_profile_pictureFacebook / Messenger: Get profile pictureA
Read-onlyIdempotent
Inspect

Download the current picture of a resolved Facebook profile; signed public picture URLs can expire.

Inputs: user_id (required), account_id.

facebook_get_user_presenceFacebook / Messenger: Get user presenceA
Read-onlyIdempotent
Inspect

Read another Facebook user's presence; not the account owner's presence.

Inputs: user_id (required), account_id.

facebook_list_comment_reactionsFacebook / Messenger: List comment reactionsA
Read-onlyIdempotent
Inspect

List visible reactions on the selected comment; counters do not prove list completeness.

Inputs: post_id (required), comment_id (required), limit, cursor, +1 more.

facebook_list_comment_repliesFacebook / Messenger: List comment repliesC
Read-onlyIdempotent
Inspect

List one page of replies; preserve the post/comment pair.

Inputs: post_id (required), comment_id (required), limit, cursor, +1 more.

facebook_list_contactsFacebook / Messenger: List contactsA
Read-onlyIdempotent
Inspect

List ranked Messenger contacts, not an exhaustive address book. No cursor/offset pagination.

Inputs: limit, account_id.

facebook_list_followersFacebook / Messenger: List followersA
Read-onlyIdempotent
Inspect

List visible followers by cursor. Missing profile tabs or partial lists do not prove zero followers. Page lists may require that activated identity.

Inputs: user_id (required), cursor, account_id.

facebook_list_followingFacebook / Messenger: List followingC
Read-onlyIdempotent
Inspect

List visible following by cursor; do not infer completeness from a missing tab.

Inputs: user_id (required), cursor, account_id.

facebook_list_friend_requestsFacebook / Messenger: List friend requestsA
Read-onlyIdempotent
Inspect

List received friend requests by cursor, or the 20 most recent sent requests (no sent cursor). Facebook request.id is the other person's numeric ID; reuse the returned request.id.

Inputs: type (required), cursor, account_id.

facebook_list_friendsFacebook / Messenger: List friendsA
Read-onlyIdempotent
Inspect

List the account owner's friends, cursor by cursor. Other users' friend lists are unavailable.

Inputs: limit, cursor, account_id.

facebook_list_inbox_chatsFacebook / Messenger: List inbox chatsB
Read-onlyIdempotent
Inspect

List one explicitly selected personal or Page inbox by cursor. Keep full Page chat IDs and enumerate every requested inbox; this is one page, not an exhaustive digest.

Inputs: inbox_id (required), type, after, limit, +5 more.

facebook_list_inboxesFacebook / Messenger: List inboxesA
Read-onlyIdempotent
Inspect

Discover personal folders and activated Pages. Choose the intended identity before reading or answering. Each Page has an independent product status; partial/degraded does not guarantee every Page is usable.

Inputs: account_id.

facebook_list_my_commentsFacebook / Messenger: List my commentsB
Read-onlyIdempotent
Inspect

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

Inputs: user_id (required), limit, cursor, account_id.

facebook_list_my_reactionsFacebook / Messenger: List my reactionsC
Read-onlyIdempotent
Inspect

Read your own or an activated Page's reaction activity log.

Inputs: user_id (required), limit, cursor, account_id.

facebook_list_post_commentsFacebook / Messenger: List post commentsA
Read-onlyIdempotent
Inspect

List one page of Facebook comments; follow next_cursor with the same post.

Inputs: post_id (required), limit, cursor, sort_by, +1 more.

facebook_list_post_reactionsFacebook / Messenger: List post reactionsA
Read-onlyIdempotent
Inspect

List visible post reactions. Facebook may omit reactors despite nonzero counters; never claim exhaustive coverage.

Inputs: post_id (required), limit, cursor, account_id.

facebook_list_recent_messagesFacebook / Messenger: List recent messagesA
Read-onlyIdempotent
Inspect

Read a bounded date-window digest from ONE explicitly selected Facebook personal/Page inbox. Enumerate requested inboxes separately. Preserve complete=false; never call a partial digest exhaustive.

Inputs: after (required), inbox_id (required), chat_type (required), max_chats (required), +3 more.

facebook_list_user_postsFacebook / Messenger: List user postsA
Read-onlyIdempotent
Inspect

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

Inputs: user_id (required), limit, cursor, account_id.

facebook_remove_comment_reactionFacebook / Messenger: Remove comment reactionA
Destructive
Inspect

Remove this identity's selected comment reaction. External action: preserve explicit user approval. Never retry after an uncertain failure; inspect current state first.

Inputs: post_id (required), react_as (required), reaction (required), comment_id (required), +1 more.

facebook_remove_friendFacebook / Messenger: Remove friendA
Destructive
Inspect

Remove this resolved Facebook friend. External action: preserve explicit user approval. Never retry after an uncertain failure; inspect current state first.

Inputs: user_id (required), account_id.

facebook_remove_post_reactionFacebook / Messenger: Remove post reactionA
Destructive
Inspect

Remove this identity's selected reaction. External action: preserve explicit user approval. Never retry after an uncertain failure; inspect current state first.

Inputs: post_id (required), react_as (required), reaction (required), account_id.

facebook_reply_to_commentFacebook / Messenger: Reply to commentA
Destructive
Inspect

Reply to this post's selected comment as the explicit identity, with at most one image. External action: preserve explicit user approval. Never retry after an uncertain failure; inspect current state first.

Inputs: text (required), post_id (required), comment_as (required), comment_id (required), +2 more.

facebook_resolve_personFacebook / Messenger: Resolve personA
Read-onlyIdempotent
Inspect

Resolve a name in the account owner's friends, bounded to five pages. Ambiguity or incomplete enumeration returns candidates without selecting anyone; no message or request is sent.

Inputs: name (required), account_id.

facebook_resolve_postFacebook / Messenger: Resolve postA
Read-onlyIdempotent
Inspect

Verify a Facebook post ID or numeric permalink (//posts/ or permalink.php?story_fbid=&id=). Other URLs require facebook_list_user_posts; never infer missing IDs.

Inputs: post_id_or_url (required), account_id.

facebook_send_friend_requestFacebook / Messenger: Send friend requestA
Destructive
Inspect

Send a friend request without a note to the resolved person. External action: preserve explicit user approval. Never retry after an uncertain failure; inspect current state first.

Inputs: user_id (required), account_id.

facebook_start_conversation_from_inboxFacebook / Messenger: Start conversation from inboxA
Destructive
Inspect

Start a personal Facebook conversation from an explicit personal inbox. Pages cannot start conversations; reply in an existing Page chat instead. External action: preserve explicit user approval. Never retry after an uncertain failure; inspect current state first.

Inputs: text (required), inbox_id (required), users_ids (required), name, +2 more.

facebook_unfollow_userFacebook / Messenger: Unfollow userA
Destructive
Inspect

Unfollow the resolved Facebook person or Page. External action: preserve explicit user approval. Never retry after an uncertain failure; inspect current state first.

Inputs: user_id (required), account_id.

facebook_update_chatFacebook / Messenger: Update chatB
Destructive
Inspect

Update requested Facebook chat name, picture, read/archive or mute state. Pins and labels are unavailable. External action: preserve explicit user approval. Never retry after an uncertain failure; inspect current state first.

Inputs: chat_id (required), name, picture, account_id, +3 more.

facebook_update_commentFacebook / Messenger: Update commentA
Destructive
Inspect

Edit the selected Facebook comment's text. External action: preserve explicit user approval. Never retry after an uncertain failure; inspect current state first.

Inputs: text (required), post_id (required), comment_id (required), account_id.

facebook_update_my_profileFacebook / Messenger: Update my profileA
Destructive
Inspect

Update only your own bio or profile picture; names and other profile fields are unsupported. External action: preserve explicit user approval. Never retry after an uncertain failure; inspect current state first.

Inputs: bio, picture, account_id.

facebook_update_postFacebook / Messenger: Update postA
Destructive
Inspect

Edit post text only, preserving media and audience. External action: preserve explicit user approval. Never retry after an uncertain failure; inspect current state first.

Inputs: text (required), post_id (required), account_id.

feedback_report_bugFeedback: Report bugA
Destructive
Inspect

Report a bug to the Nilyo team as a tracked issue. Use after a tool failed unexpectedly (TOOL_FAILED, wrong or empty result, broken flow) and the user agrees to report it; also when the user says 'ça ne marche pas' / 'report this'. Include the exact error code and details from the failing result so engineers can reproduce. Never include credentials, message bodies or third-party personal data. Ask the user for consent first (user_consent=true).

Inputs: title (required), description (required), user_consent (required), tool, +9 more.

feedback_request_featureFeedback: Request featureA
Destructive
Inspect

Send a feature request or improvement idea to the Nilyo team as a tracked issue: a missing action, provider or capability, a workflow that needs too many steps, a confusing result. Use when the user asks for something Nilyo cannot do yet, or explicitly wants to suggest an improvement, and agrees to send it. Describe the user's goal and why current tools fall short. Ask the user for consent first (user_consent=true).

Inputs: title (required), description (required), user_consent (required), tool, +3 more.

imap_connectIMAP: ConnectA
Destructive
Inspect

Connect a generic IMAP/SMTP mailbox directly from the conversation with the mailbox credentials (credentials are entered in this tool; account_connect provides a secure browser form). Nilyo forwards the credentials once to the connection service and never stores them. Start with user + password only (servers are auto-detected); if the result says the IMAP or SMTP configuration is invalid, ask the user for the servers (e.g. OVH: imap ssl0.ovh.net:993 ssl, smtp ssl0.ovh.net:465 ssl; Gmail/Microsoft mailboxes should use the Google/Outlook connection instead). Use account_id to re-authenticate an existing disconnected IMAP account.

Inputs: user (required), password (required), imap_host, imap_port, +6 more.

instagram_comment_on_postInstagram: Comment on postA
Destructive
Inspect

Publish an approved top-level text comment on one exact Instagram post. Resolve/read the post first; reuse post.id, then read comments for context. This does not reply to a specific comment. No attachments or comment_as are supported here. Publish only the exact user-requested/approved text and target. Never automatically retry a failed, partial or timed-out write: inspect instagram_list_post_comments before deciding another send.

Inputs: text (required), post_id (required), account_id.

instagram_create_postInstagram: Create postA
Destructive
Inspect

Publish an Instagram photo post or carousel (ordered image/video attachments) from the selected owned account. Media is required; text-only posts are unsupported. One video publishes as a Reel: prefer instagram_create_reel for that intent. Stories use instagram_create_story, not this route. Publish only after explicit approval of the final media, caption, format and connected account. Never automatically retry a timeout, failed read-back or ambiguous write: creation may have succeeded. Preserve the receipt and inspect instagram_list_user_posts(user_id='me') / instagram_get_post before any further post or Reel; for a Story ask the user to check Instagram because no Story listing tool is exposed.

Inputs: text (required), attachments (required), account_id.

instagram_create_reelInstagram: Create reelA
Destructive
Inspect

Publish an Instagram Reel (réel): exactly one video, with the approved caption. V2 creates the Reel through POST /posts based on the video MIME type; no invented reel endpoint or post_type is needed. Use instagram_create_post for photo/carousel and instagram_create_story for a Story. Publish only after explicit approval of the final media, caption, format and connected account. Never automatically retry a timeout, failed read-back or ambiguous write: creation may have succeeded. Preserve the receipt and inspect instagram_list_user_posts(user_id='me') / instagram_get_post before any further post or Reel; for a Story ask the user to check Instagram because no Story listing tool is exposed.

Inputs: text (required), attachment (required), account_id.

instagram_create_storyInstagram: Create storyA
Destructive
Inspect

Publish an Instagram Story with exactly one image or video through the separate V2 Story route. Optional text supports @username mentions; do not promise a visible caption overlay or arbitrary stickers/music/effects. This is not a feed post or Reel. Publish only after explicit approval of the final media, caption, format and connected account. Never automatically retry a timeout, failed read-back or ambiguous write: creation may have succeeded. Preserve the receipt and inspect instagram_list_user_posts(user_id='me') / instagram_get_post before any further post or Reel; for a Story ask the user to check Instagram because no Story listing tool is exposed.

Inputs: attachment (required), text, account_id.

instagram_follow_userInstagram: Follow userA
Destructive
Inspect

Follow one exact Instagram account from the selected owned account. Resolve/disambiguate with instagram_get_profile or instagram_get_profile_from_url, then use numeric profile.id, never specifics.messaging_identifier. Requires explicit user intent/approval. Preserve the native receipt: UserFollowed means followed; RelationRequest means a follow request was sent to a private account, not accepted. Never automatically retry a failed or ambiguous write; read the profile/following state first.

Inputs: user_id (required), account_id.

instagram_get_my_profileInstagram: Get my profileA
Read-onlyIdempotent
Inspect

Get the profile of the owner of the connected Instagram account.

Inputs: account_id.

instagram_get_postInstagram: Get postA
Read-onlyIdempotent
Inspect

Read and resolve an Instagram post from its shortcode or Instagram post/reel URL before liking or commenting. Reuse returned post.id; confirm the post and author. URLs are parsed locally, never fetched.

Inputs: post_id_or_url (required), account_id.

instagram_get_profileInstagram: Get profileA
Read-onlyIdempotent
Inspect

Resolve an Instagram username or @handle to a profile; for URLs use instagram_get_profile_from_url. Reuse numeric profile.id for instagram_list_user_posts and instagram_follow_user; specifics.messaging_identifier is only for messaging.

Inputs: user_id (required), account_id.

instagram_get_profile_from_urlInstagram: Get profile from URLA
Read-onlyIdempotent
Inspect

Resolve an Instagram profile URL or @handle to the exact profile before posts/follow actions. Only Instagram profile URLs are parsed; no arbitrary URL is fetched. Reuse numeric profile.id, never specifics.messaging_identifier, and disambiguate the intended identity.

Inputs: profile_url (required), account_id.

instagram_like_postInstagram: Like postA
Destructive
Inspect

Like one exact Instagram post from the selected owned Instagram account. Read/resolve the post with instagram_get_post or instagram_list_user_posts first and reuse post.id. Sends the fixed V2 reaction instagram_like; no arbitrary reaction. Act only on the user's explicit request/approval. Never automatically retry a failed or ambiguous write; inspect the post's user_reacted state first.

Inputs: post_id (required), account_id.

instagram_list_conversationsInstagram: List conversationsA
Read-onlyIdempotent
Inspect

List Instagram DM conversations from the user's own account. Use to locate a chat before reading/replying.

Inputs: limit, account_id.

instagram_list_followersInstagram: List followersC
Read-onlyIdempotent
Inspect

List followers of the connected Instagram account or a known Instagram user where supported.

Inputs: user_id (required), limit, cursor, offset, +1 more.

instagram_list_followingInstagram: List followingB
Read-onlyIdempotent
Inspect

List Instagram accounts followed by the connected account/user where supported.

Inputs: user_id (required), limit, cursor, offset, +1 more.

instagram_list_post_commentsInstagram: List post commentsA
Read-onlyIdempotent
Inspect

Read comments on an exact Instagram post before composing a comment or checking whether an earlier uncertain comment was applied. Resolve post.id with instagram_list_user_posts/instagram_get_post first. Cursor pagination only; preserve account/post and sort order with next_cursor, no offset.

Inputs: post_id (required), limit, cursor, sort_by, +1 more.

instagram_list_user_postsInstagram: List user postsA
Read-onlyIdempotent
Inspect

List posts authored by another resolved Instagram account or 'me'. Resolve a username with instagram_get_profile or a profile URL with instagram_get_profile_from_url, then reuse numeric profile.id. Results include post.id (shortcode) for likes/comments. Cursor pagination only: preserve account_id/user_id with next_cursor, no offset. One page is not an exhaustive list; private accounts depend on the connected account's access.

Inputs: user_id (required), limit, cursor, account_id.

instagram_read_conversationInstagram: Read conversationA
Read-onlyIdempotent
Inspect

Read an Instagram DM conversation and recent messages for context, lead qualification or follow-up workflows.

Inputs: chat_id (required), account_id.

instagram_send_messageInstagram: Send messageA
Destructive
Inspect

Send an Instagram DM in an existing conversation from the user's own account. Locate chat_id first if necessary and only send after clear user approval.

Inputs: text (required), chat_id (required), account_id.

instagram_update_my_profileInstagram: Update my profileB
Destructive
Inspect

Update supported fields on the user's own Instagram profile. Only pass fields explicitly requested; availability is provider-dependent.

Inputs: bio, picture, account_id.

linkedin_accept_invitationLinkedIn: Accept invitationA
Destructive
Inspect

Accept a received LinkedIn connection request. Requires request_id from linkedin_list_invitations(type='received').

Inputs: request_id (required), account_id.

linkedin_cancel_or_refuse_invitationLinkedIn: Cancel or refuse invitationA
Destructive
Inspect

Withdraw a sent LinkedIn invitation or refuse a received invitation. First list the relevant invitations to obtain request_id unless it is already known.

Inputs: request_id (required), account_id.

linkedin_classic_get_applicant_resumeLinkedIn: Classic get applicant resumeA
Read-onlyIdempotent
Inspect

Download/retrieve the resume of one applicant to a LinkedIn Classic job. Never infer applicant_id from name; list applicants first and reuse exact applicant.id.

Inputs: job_id (required), applicant_id (required), account_id.

linkedin_classic_get_job_applicantLinkedIn: Classic get job applicantA
Read-onlyIdempotent
Inspect

Get one applicant to a LinkedIn Classic job. Required chain: owned Classic job -> job_id -> list applicants -> applicant.id -> this tool.

Inputs: job_id (required), applicant_id (required), account_id.

linkedin_classic_list_job_applicantsLinkedIn: Classic list job applicantsA
Read-onlyIdempotent
Inspect

List applicants for a LinkedIn Classic job owned by the connected account. Resolve the exact Classic job_id first. Filters are passed as V2 applicant filters (for example ratings/experience) and must use provider enums/IDs rather than guessed display values.

Inputs: job_id (required), filters, account_id.

linkedin_comment_on_postLinkedIn: Comment on postA
Destructive
Inspect

Publish a top-level LinkedIn comment as the connected person, or as a managed company page using comment_as from linkedin_list_managed_company_pages. Requires post_id. Use after reading the post/comments and only when the user has asked to publish the final reply.

Inputs: text (required), post_id (required), account_id, comment_as.

linkedin_create_postLinkedIn: Create postA
Destructive
Inspect

Publish a LinkedIn post from the user's own account, optionally on a managed company page using post_as from linkedin_list_managed_company_pages. This is a public side effect; use only after the user has clearly approved the final content and target identity.

Inputs: text (required), post_as, can_read, account_id, +2 more.

linkedin_endorse_skillLinkedIn: Endorse skillA
Destructive
Inspect

Endorse one skill on a LinkedIn relation. Resolve member_id first, fetch that profile with linkedin_skills, and reuse the exact returned endorsement skill_id; never pass a skill name.

Inputs: skill_id (required), member_id (required), account_id.

linkedin_follow_userLinkedIn: Follow userA
Destructive
Inspect

Follow a LinkedIn user from the connected personal account. Resolve the exact provider user_id first.

Inputs: user_id (required), account_id.

linkedin_get_companyLinkedIn: Get companyA
Read-onlyIdempotent
Inspect

Get a LinkedIn company profile by numeric/provider company ID. Use after linkedin_search_companies when full company data is needed.

Inputs: company_id (required), account_id.

linkedin_get_company_follow_creditsLinkedIn: Get company follow creditsA
Read-onlyIdempotent
Inspect

Read the remaining LinkedIn credits for inviting members to follow a company page administered by the connected account: remaining_credit, credit_grant per reset and resets_on (ISO 8601 UTC). Use before linkedin_send_company_follow_invitation or after a credit-limit error. Requires the numeric company ID of an administered page (linkedin_list_managed_company_pages).

Inputs: company_id (required), account_id.

linkedin_get_inmail_creditsLinkedIn: Get InMail creditsA
Read-onlyIdempotent
Inspect

Get LinkedIn InMail credit information for the connected account. Use when the user asks whether an InMail can be sent or how many credits remain.

Inputs: account_id.

linkedin_get_job_postingLinkedIn: Get job postingA
Read-onlyIdempotent
Inspect

Get one job posting owned by the user's LinkedIn account. job_posting_id MUST come from linkedin_list_job_postings, not a title/company or an unrelated discovery result. LinkedIn job ID: Exact LinkedIn job/job-posting ID returned by the corresponding search/list endpoint. Obtain with: linkedin_search_jobs -> result.id for discovery; linkedin_list_job_postings -> result.id for jobs owned by the account Never pass: job title, company ID.

Inputs: job_posting_id (required), account_id.

linkedin_get_job_posting_budgetLinkedIn: Get job posting budgetA
Read-onlyIdempotent
Inspect

Get budget/pricing information for a LinkedIn Classic job posting owned by the connected account. Resolve job_id with linkedin_list_job_postings first.

Inputs: job_id (required), account_id.

linkedin_get_my_profileLinkedIn: Get my profileA
Read-onlyIdempotent
Inspect

Get the profile of the owner of the connected LinkedIn account. Use for 'my LinkedIn profile', identity/context, or before actions that need the account owner's provider user ID.

Inputs: account_id.

linkedin_get_postLinkedIn: Get postA
Read-onlyIdempotent
Inspect

Get a LinkedIn post by its provider post_id. Use when you already know a post_id and need full post context.

Inputs: post_id (required), account_id.

linkedin_get_profileLinkedIn: Get profileB
Read-onlyIdempotent
Inspect

Get a LinkedIn person's full profile from a LinkedIn provider user ID, public identifier, or linkedin.com/in/... URL using the user's own account. Use it to retrieve a profile and resolve its stable ID from a supplied URL. The result contains the stable user id needed by linkedin_start_conversation and linkedin_send_invitation. Optional sections can retrieve experience, skills, interests and other profile details.

Inputs: user_id_or_url (required), variant, account_id, with_sections.

linkedin_get_profile_from_urlLinkedIn: Get profile from URLA
Read-onlyIdempotent
Inspect

Resolve a full LinkedIn person profile URL into the real LinkedIn profile and stable system user ID required by downstream actions. Example: https://www.linkedin.com/in/john-doe-123/?trk=foo -> extract ONLY 'john-doe-123' from the /in/{public_identifier}/ pathname, ignore query parameters/fragments/trailing slash, call Get User Profile, and return the profile including result.id. Use result.id for connection requests, new conversations and other actions requiring user_id. Never pass the full URL to those action tools. LinkedIn system user ID: Stable LinkedIn user id, commonly ACo... for Classic profiles. Obtain with: linkedin_get_profile_from_url(profile_url) -> result.id; linkedin_get_profile(user_id_or_public_identifier) -> result.id; linkedin_search_people(...) -> selected result.id Never pass: full linkedin.com/in/... URL, person name, company ID. LinkedIn public identifier: Slug after /in/ in a LinkedIn profile URL. Example https://www.linkedin.com/in/john-doe/?trk=x -> john-doe. Obtain with: extract only pathname segment immediately after /in/; ignore query string, fragment and trailing slash Never pass: full URL, ACo system ID when a public identifier is specifically required.

Inputs: profile_url (required), account_id, with_sections.

linkedin_get_search_parametersLinkedIn: Get search parametersA
Read-onlyIdempotent
Inspect

Resolve human LinkedIn filter values such as a location, company, industry, job function, relation, project, saved search or Sales Navigator list into the provider parameter IDs required by LinkedIn search endpoints. Typical sequence: call this with type + query, then pass the chosen returned id into linkedin_search_people / Sales Navigator / Recruiter search.

Inputs: type (required), product (required), query, account_id.

linkedin_list_comment_repliesLinkedIn: List comment repliesA
Read-onlyIdempotent
Inspect

List replies under one exact LinkedIn comment. Chain: resolve post -> post.id -> list comments -> comment.id -> replies. Post ID: Exact provider post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it. Comment ID: Exact comment id scoped to the identified post. Obtain with: linkedin_list_post_comments(post_id) -> comment.id; instagram_list_post_comments(post_id) -> comment.id Never pass: comment text, post_id.

Inputs: post_id (required), comment_id (required), offset, account_id.

linkedin_list_contractsLinkedIn: List contractsA
Read-onlyIdempotent
Inspect

List LinkedIn premium contracts available on the user's account. Returned contract.id is the ONLY value to pass as contract_id to linkedin_select_contract. contract_id is distinct from inbox_id. LinkedIn premium contract ID: Exact Sales Navigator/Recruiter contract id. Obtain with: linkedin_list_contracts -> contract.id Never pass: inbox_id, product name. Inbox ID: Provider inbox/product inbox identifier. LinkedIn Classic may use CLASSIC; premium products expose their own inbox IDs. Obtain with: linkedin_list_inboxes -> inbox.id Never pass: contract_id unless returned as the inbox id, guessing SALES_NAVIGATOR or RECRUITER.

Inputs: account_id.

linkedin_list_conversationsLinkedIn: List conversationsA
Read-onlyIdempotent
Inspect

List LinkedIn private conversations. By default only the Classic primary inbox (CLASSIC_PRIMARY); pass inbox_ids from linkedin_list_inboxes to read other inboxes (archived, spam, Sales Navigator, Recruiter, company pages). Inboxes are read one after another to respect LinkedIn rate limits; unreadable ones are reported with unavailable instead of failing. Preserve inbox_id and chat.id. Use before linkedin_read_conversation when chat_id is unknown.

Inputs: limit, inbox_ids, account_id.

linkedin_list_followersLinkedIn: List followersB
Read-onlyIdempotent
Inspect

List followers of the account owner or a known LinkedIn user. Use user_id='me' for the connected account owner.

Inputs: user_id (required), offset, account_id.

linkedin_list_followingLinkedIn: List followingA
Read-onlyIdempotent
Inspect

List LinkedIn users followed by the connected account owner. Prefer user_id='me'; provider availability may restrict following data for other users.

Inputs: user_id (required), offset, account_id.

linkedin_list_inbox_chatsLinkedIn: List inbox chatsA
Read-onlyIdempotent
Inspect

List chats from a specific LinkedIn inbox. Use for LinkedIn V2 and premium Sales Navigator/Recruiter inboxes; account-wide chat listing is unsupported. Get inbox_id from linkedin_list_inboxes. Pages are capped at 20; follow every cursor and list each intended inbox separately. A page is not an exhaustive digest. With cursor, the page size of the first page is kept (limit is ignored).

Inputs: inbox_id (required), after, limit, before, +3 more.

linkedin_list_inboxesLinkedIn: List inboxesA
Read-onlyIdempotent
Inspect

List LinkedIn messaging inboxes for Classic, Sales Navigator and Recruiter. Use before listing inbox chats or starting Sales Navigator/Recruiter conversations; premium products require the appropriate primary inbox.

Inputs: account_id.

linkedin_list_invitationsLinkedIn: List invitationsA
Read-onlyIdempotent
Inspect

List pending LinkedIn connection/relation requests sent or received by the account owner. Use before accepting/refusing a received invitation or withdrawing a sent invitation so you have the required request_id.

Inputs: type (required), account_id.

linkedin_list_job_postingsLinkedIn: List job postingsA
Read-onlyIdempotent
Inspect

List LinkedIn job postings OWNED by the user's account. Use this to resolve job_posting_id for management/budget operations. This differs from linkedin_search_jobs, which discovers jobs across LinkedIn.

Inputs: state (required), limit, offset, account_id.

linkedin_list_managed_company_pagesLinkedIn: List managed company pagesA
Read-onlyIdempotent
Inspect

Discover the LinkedIn company pages this connected account administers. Reuse the selected data[].id (NOT mailbox_id) with the SAME account_id as post_as for linkedin_create_post, comment_as for linkedin_comment_on_post/linkedin_reply_to_comment, or react_as for linkedin_react_to_post/social_react_to_comment. Requires the company product selected in Hosted Auth; if access is refused, reconnect the SAME account with account_connect and select Company Pages. A company search result does not prove admin rights; never fall back to acting as the person.

Inputs: account_id.

linkedin_list_my_connectionsLinkedIn: List my connectionsA
Read-onlyIdempotent
Inspect

List/search the LinkedIn connections of the account owner. Use for questions such as 'who do I know at this company?', 'find Sarah in my network', introductions, relationship mapping and connection-aware prospecting. This reads the user's personal network rather than a company page.

Inputs: cursor, search, account_id.

linkedin_list_post_commentsLinkedIn: List post commentsA
Read-onlyIdempotent
Inspect

List comments on a LinkedIn post. Requires post_id from search/list/get post. Use before deciding which comments need a reply.

Inputs: post_id (required), offset, account_id.

linkedin_list_post_reactionsLinkedIn: List post reactionsA
Read-onlyIdempotent
Inspect

List people/reactions on a LinkedIn post. Use for engagement analysis or to identify who reacted.

Inputs: post_id (required), offset, account_id.

linkedin_list_user_postsLinkedIn: List user postsA
Read-onlyIdempotent
Inspect

List posts authored by the connected LinkedIn user or a known provider user ID. Use to locate a recent post and obtain its post_id before reading comments/reactions or replying.

Inputs: user_id (required), offset, account_id.

linkedin_list_user_relationsLinkedIn: List user relationsB
Read-onlyIdempotent
Inspect

List a LinkedIn user's visible relations by provider user ID. Use when network graph context is requested for a known profile.

Inputs: user_id (required), cursor, search, account_id.

linkedin_react_to_messageLinkedIn: React to messageA
Destructive
Inspect

Add a reaction to a specific LinkedIn message. Requires chat_id and message_id, normally discovered by reading the conversation.

Inputs: chat_id (required), reaction (required), message_id (required), account_id.

linkedin_react_to_postLinkedIn: React to postA
Destructive
Inspect

Like/react to a LinkedIn post as the connected person, or as a managed company page using react_as from linkedin_list_managed_company_pages. Use a supported LinkedIn reaction value and only when the user's intent to react is clear.

Inputs: post_id (required), reaction (required), react_as, account_id.

linkedin_read_conversationLinkedIn: Read conversationA
Read-onlyIdempotent
Inspect

Read a LinkedIn private conversation plus recent messages. Use before replying so the agent understands prior context, commitments and tone.

Inputs: chat_id (required), account_id.

linkedin_recruiter_get_applicantLinkedIn: Recruiter get applicantA
Read-onlyIdempotent
Inspect

Get one Recruiter applicant. Required chain: list/select Hiring Project -> project.id -> list applicants -> applicant.id. applicant_id is scoped to the selected project context.

Inputs: project_id (required), applicant_id (required), account_id.

linkedin_recruiter_get_applicant_resumeLinkedIn: Recruiter get applicant resumeA
Read-onlyIdempotent
Inspect

Retrieve a Recruiter applicant resume. Resolve exact project_id and applicant_id first; never use candidate name or LinkedIn URL as applicant_id.

Inputs: project_id (required), applicant_id (required), account_id.

linkedin_recruiter_list_applicantsLinkedIn: Recruiter list applicantsA
Read-onlyIdempotent
Inspect

List applicants from a LinkedIn Recruiter Hiring Project talent pool. Resolve project_id first. Recruiter applicants are project-scoped; never substitute a Classic job_id for project_id.

Inputs: project_id (required), limit, cursor, filters, +1 more.

linkedin_recruiter_search_peopleLinkedIn: Recruiter search peopleA
Read-onlyIdempotent
Inspect

Search LinkedIn Recruiter candidates using the user's Recruiter-capable account. Use for candidate sourcing, recruiting projects/talent pools and Recruiter-specific filters. Resolve filter IDs with linkedin_get_search_parameters(product='recruiter') when necessary. This read tool cannot save searches or custom filters.

Inputs: account_id, save_search, save_custom_filter.

linkedin_remove_connectionLinkedIn: Remove connectionA
Destructive
Inspect

Remove an existing LinkedIn relation/connection. Resolve the exact provider user_id first. This changes the user's network and requires explicit intent.

Inputs: user_id (required), account_id.

linkedin_reply_to_commentLinkedIn: Reply to commentA
Destructive
Inspect

Reply DIRECTLY to one exact LinkedIn comment as the connected person, or as a managed company page using comment_as from linkedin_list_managed_company_pages. Confirm the final text and target identity before publishing. Required chain from human reference: resolve post -> post.id -> list comments -> comment.id -> optionally read replies -> reply. Post ID: Exact provider post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it. Comment ID: Exact comment id scoped to the identified post. Obtain with: linkedin_list_post_comments(post_id) -> comment.id; instagram_list_post_comments(post_id) -> comment.id Never pass: comment text, post_id.

Inputs: text (required), post_id (required), comment_id (required), account_id, +1 more.

linkedin_resolve_companyLinkedIn: Resolve companyA
Read-onlyIdempotent
Inspect

Resolve a human company name to LinkedIn company results and exact company IDs. Use before employee searches, company profile reads or company mentions. LinkedIn company mentions require the numeric company ID; the slug from /company/google/ is not sufficient. LinkedIn company ID: Provider numeric/company ID. For mentions LinkedIn requires numeric company ID, not the company URL slug. Obtain with: linkedin_search_companies -> selected result.id; linkedin_get_company after resolving a company Never pass: linkedin.com/company/google URL, company slug such as google, company name.

Inputs: keywords (required), filters, account_id, save_search, +1 more.

linkedin_resolve_my_postLinkedIn: Resolve my postB
Read-onlyIdempotent
Inspect

Resolve a user's description such as 'my latest post' into exact post IDs before comments/reactions/edit/delete. Returns the account owner's posts; choose the matching post and reuse result.id. Post ID: Exact provider post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it.

Inputs: offset, account_id.

linkedin_resolve_personLinkedIn: Resolve personA
Read-onlyIdempotent
Inspect

Resolve a human description (name, role, employer, location keywords) to LinkedIn people and their stable system IDs before an action. Use when the user says 'message Sarah at Acme' or 'connect with the CTO of X' rather than providing an ID. If multiple plausible results remain, show/disambiguate them before any write. LinkedIn system user ID: Stable LinkedIn user id, commonly ACo... for Classic profiles. Obtain with: linkedin_get_profile_from_url(profile_url) -> result.id; linkedin_get_profile(user_id_or_public_identifier) -> result.id; linkedin_search_people(...) -> selected result.id Never pass: full linkedin.com/in/... URL, person name, company ID.

Inputs: keywords (required), limit, filters, account_id, +2 more.

linkedin_sales_navigator_search_peopleLinkedIn: Sales Navigator search peopleA
Read-onlyIdempotent
Inspect

Search LinkedIn Sales Navigator leads using the user's own Sales Navigator-capable LinkedIn account. Use for advanced prospecting intent such as lead lists, seniority, years of experience, current/past company, geography, function and saved-search criteria. Resolve human filter names to LinkedIn IDs with linkedin_get_search_parameters(product='sales_navigator') when necessary. This read tool cannot save searches or custom filters.

Inputs: account_id, save_search, save_custom_filter.

linkedin_search_companiesLinkedIn: Search companiesA
Read-onlyIdempotent
Inspect

Search LinkedIn companies from the user's own account. Use to find a company ID/profile before looking for employees, checking network relationships or performing a people search scoped to that company.

Inputs: industry, keywords, location, account_id, +4 more.

linkedin_search_from_urlLinkedIn: Search from URLA
Read-onlyIdempotent
Inspect

Run a native LinkedIn search from a LinkedIn search URL. Use when the user pastes a linkedin.com/search/results/... URL, Sales Navigator search URL or Recruiter search URL and wants the same filters/results available to the agent.

Inputs: url (required), product (required), account_id.

linkedin_search_jobsLinkedIn: Search jobsA
Read-onlyIdempotent
Inspect

Search LinkedIn jobs with the user's own account. Use for job discovery by keywords, title, company, location, seniority, employment status or workplace type.

Inputs: keywords, job_title, account_id, date_posted, +3 more.

linkedin_search_peopleLinkedIn: Search peopleA
Read-onlyIdempotent
Inspect

Search LinkedIn Classic people with the user's own LinkedIn account. Use to find a person/provider user ID from a name, title, employer, location, industry, keywords or network distance. When the next requested action is message/invitation, take the chosen result's id and pass it to the action tool; never pass a profile URL directly to an action requiring user_id. Some filters require IDs; resolve them first with linkedin_get_search_parameters.

Inputs: cursor, school, service, industry, +13 more.

linkedin_search_postsLinkedIn: Search postsA
Read-onlyIdempotent
Inspect

Search LinkedIn posts using the user's own account. Use to find a post before reading comments, checking reactions or replying. Returns post IDs required by comment/reaction tools.

Inputs: sort_by, keywords, account_id, date_posted, +3 more.

linkedin_select_contractLinkedIn: Select contractA
Destructive
Inspect

Select a LinkedIn Sales Navigator/Recruiter premium contract. First call linkedin_list_contracts and reuse exact contract.id. Do not pass product name or inbox_id. LinkedIn premium contract ID: Exact Sales Navigator/Recruiter contract id. Obtain with: linkedin_list_contracts -> contract.id Never pass: inbox_id, product name.

Inputs: contract_id (required), account_id.

linkedin_send_company_follow_invitationLinkedIn: Send company follow invitationA
Destructive
Inspect

Invite one or more Classic LinkedIn members to follow a company page administered by the connected account, in one provider request. Resolve/disambiguate the numeric company and each Classic ACo member first; linkedin_get_company_follow_credits shows remaining invitation credits. Send only when the user explicitly requested/approved this exact page, recipients and account; otherwise ask for confirmation under the common MCP action rules. This is distinct from a connection invitation or following a company yourself. LinkedIn enforces page permissions, recipient eligibility and invitation credits. The receipt returns created invitation IDs and success/failed counts; it confirms creation only, not acceptance or a new follower, and does not say which members failed. No listing, acceptance or withdrawal is supported. Never retry automatically, including failed recipients, provider errors, rate limits and timeouts. After a partial or ambiguous failure the user must inspect LinkedIn before deciding any further send; no MCP invitation-state lookup exists for this action.

Inputs: company_id (required), member_ids (required), account_id.

linkedin_send_invitationLinkedIn: Send invitationA
Destructive
Inspect

Send a LinkedIn connection/relation request from the user's own account. Requires a provider user_id, not a profile URL. If the user supplied a URL or name, FIRST call linkedin_get_profile or linkedin_search_people and use the returned id. Include a note only when explicitly requested or clearly provided by the user.

Inputs: user_id (required), message, account_id.

linkedin_send_messageLinkedIn: Send messageA
Destructive
Inspect

Send a message in an EXISTING LinkedIn chat. Requires chat_id, normally obtained from linkedin_list_conversations. Use only when the user has clearly asked to send/approved the final text.

Inputs: text (required), chat_id (required), account_id.

linkedin_start_conversationLinkedIn: Start conversationA
Destructive
Inspect

Start a new LinkedIn conversation and send a message. Requires the stable LinkedIn provider user_id. IMPORTANT: if the user gives a LinkedIn URL, name or search criteria, first call linkedin_get_profile or linkedin_search_people, extract the returned user id, then call this tool. Do not put a LinkedIn URL into linkedin_user_id.

Inputs: text (required), linkedin_user_id (required), inbox_id, account_id.

linkedin_start_conversation_from_inboxLinkedIn: Start conversation from inboxA
Destructive
Inspect

Start a LinkedIn Classic, Sales Navigator or Recruiter conversation from an explicit inbox. Resolve recipient user IDs first and obtain inbox_id with linkedin_list_inboxes. For Sales Navigator include the required subject in specifics; Recruiter may require subject and signature. Supports one-to-one or group recipients and attachments.

Inputs: text (required), inbox_id (required), users_ids (required), name, +3 more.

linkedin_submit_company_member_otpLinkedIn: Submit company member OTPA
Destructive
Inspect

Complete LinkedIn company-member verification. Reuse the same email and exact challenge_id returned by linkedin_verify_company_member_email, and submit only the real user-provided code; never invent or loop over codes.

Inputs: code (required), email (required), product (required), company_id (required), +2 more.

linkedin_unfollow_userLinkedIn: Unfollow userA
Destructive
Inspect

Unfollow a LinkedIn user from the connected account. Resolve the exact provider user_id first.

Inputs: user_id (required), account_id.

linkedin_update_my_profileLinkedIn: Update my profileB
Destructive
Inspect

Update supported fields of the user's own LinkedIn profile. Only pass fields explicitly requested by the user; provider support varies by field.

Inputs: bio, picture, summary, headline, +4 more.

linkedin_verify_company_member_emailLinkedIn: Verify company member emailA
Destructive
Inspect

Start LinkedIn company-member identity verification when a job/company action fails with insufficient permissions. Resolve company_id first and submit the actual verification email. Preserve the returned challenge_id for linkedin_submit_company_member_otp.

Inputs: email (required), product (required), company_id (required), account_id.

linkedin_visit_profileLinkedIn: Visit profileA
Destructive
Inspect

Report a LinkedIn profile visit using notify_visit_token returned by the resolved profile. The token is provider-issued and must not be replaced with user_id, profile URL or public identifier.

Inputs: notify_visit_token (required), account_id.

list_connected_accountsList connected accountsA
Read-onlyIdempotent
Inspect

List the user's own accounts connected to Nilyo with provider, owner display name, identifier (LinkedIn public id, phone, email), connection status and reconnection hints. Use when the user asks what is connected, when several accounts of one provider exist and the user names one ("with Julia's LinkedIn"), or after a choose_account result. Nilyo never guesses between accounts: pick the entry matching what the user said and pass its unipile_account_id as account_id to the action tool.

Inputs: provider.

message_add_reactionMessage: Add reactionA
Destructive
Inspect

Add an emoji reaction to one exact WhatsApp, Instagram, Telegram or LinkedIn message (e.g. 👍, ❤️). Resolve chat/message first; keep chat_id + message_id paired. Use message_remove_reaction to withdraw it. Chat ID: Exact provider chat/conversation ID. LinkedIn chat IDs may also be visible in /messaging/thread/{chat_id}/ URLs. Obtain with: provider list conversations/inbox chats -> chat.id Never pass: person name, user_id, message_id. Message ID: Exact message id inside a specific chat. In V2 always keep chat_id together with message_id because providers may only guarantee uniqueness inside the chat. Obtain with: provider read/list conversation messages -> message.id Never pass: message text, chat_id, message ID without its chat context for mutation tools.

Inputs: chat_id (required), reaction (required), message_id (required), account_id.

message_deleteMessage: DeleteA
Destructive
Inspect

Delete one exact message. Resolve and verify chat/message first; destructive. Chat ID: Exact provider chat/conversation ID. LinkedIn chat IDs may also be visible in /messaging/thread/{chat_id}/ URLs. Obtain with: provider list conversations/inbox chats -> chat.id Never pass: person name, user_id, message_id. Message ID: Exact message id inside a specific chat. In V2 always keep chat_id together with message_id because providers may only guarantee uniqueness inside the chat. Obtain with: provider read/list conversation messages -> message.id Never pass: message text, chat_id, message ID without its chat context for mutation tools.

Inputs: chat_id (required), message_id (required), account_id.

message_editMessage: EditA
Destructive
Inspect

Edit one previously sent message where supported. Recommended chain: resolve chat -> list messages -> message_get -> edit. Keep exact chat_id + message_id pair. Chat ID: Exact provider chat/conversation ID. LinkedIn chat IDs may also be visible in /messaging/thread/{chat_id}/ URLs. Obtain with: provider list conversations/inbox chats -> chat.id Never pass: person name, user_id, message_id. Message ID: Exact message id inside a specific chat. In V2 always keep chat_id together with message_id because providers may only guarantee uniqueness inside the chat. Obtain with: provider read/list conversation messages -> message.id Never pass: message text, chat_id, message ID without its chat context for mutation tools.

Inputs: text (required), chat_id (required), message_id (required), account_id.

message_forwardMessage: ForwardA
Destructive
Inspect

Forward an existing message to another EXISTING chat. Resolve source chat + message and destination chat independently. target_chat_id is a chat ID, never recipient user_id/name. Chat ID: Exact provider chat/conversation ID. LinkedIn chat IDs may also be visible in /messaging/thread/{chat_id}/ URLs. Obtain with: provider list conversations/inbox chats -> chat.id Never pass: person name, user_id, message_id. Message ID: Exact message id inside a specific chat. In V2 always keep chat_id together with message_id because providers may only guarantee uniqueness inside the chat. Obtain with: provider read/list conversation messages -> message.id Never pass: message text, chat_id, message ID without its chat context for mutation tools.

Inputs: chat_id (required), message_id (required), target_chat_id (required), account_id.

message_getMessage: GetA
Read-onlyIdempotent
Inspect

Get one exact message. BOTH chat_id and message_id are required because V2 message identity is contextual to its chat. If starting from a person/topic, resolve chat first, list messages, then reuse both IDs. Chat ID: Exact provider chat/conversation ID. LinkedIn chat IDs may also be visible in /messaging/thread/{chat_id}/ URLs. Obtain with: provider list conversations/inbox chats -> chat.id Never pass: person name, user_id, message_id. Message ID: Exact message id inside a specific chat. In V2 always keep chat_id together with message_id because providers may only guarantee uniqueness inside the chat. Obtain with: provider read/list conversation messages -> message.id Never pass: message text, chat_id, message ID without its chat context for mutation tools.

Inputs: chat_id (required), message_id (required), account_id.

message_get_attachmentMessage: Get attachmentA
Read-onlyIdempotent
Inspect

Download one exact attachment from a WhatsApp, Instagram, Telegram or LinkedIn message (for example a voice note or an image) as base64 bytes with its content type. Required chain: resolve/list chat -> chat_id -> get/list message -> attachment.id -> retrieve. All three IDs (chat_id, message_id, attachment_id) are required because attachment identity is scoped to its message. Chat ID: Exact provider chat/conversation ID. LinkedIn chat IDs may also be visible in /messaging/thread/{chat_id}/ URLs. Obtain with: provider list conversations/inbox chats -> chat.id Never pass: person name, user_id, message_id. Message ID: Exact message id inside a specific chat. In V2 always keep chat_id together with message_id because providers may only guarantee uniqueness inside the chat. Obtain with: provider read/list conversation messages -> message.id Never pass: message text, chat_id, message ID without its chat context for mutation tools. Attachment ID: Exact attachment id returned inside a specific email/message. Obtain with: read the parent email/message first -> attachment.id Never pass: filename, URL.

Inputs: chat_id (required), message_id (required), attachment_id (required), account_id.

message_list_reactionsMessage: List reactionsB
Read-onlyIdempotent
Inspect

List detailed reactions on one exact message. Preserve its chat_id + message_id pair. Chat ID: Exact provider chat/conversation ID. LinkedIn chat IDs may also be visible in /messaging/thread/{chat_id}/ URLs. Obtain with: provider list conversations/inbox chats -> chat.id Never pass: person name, user_id, message_id. Message ID: Exact message id inside a specific chat. In V2 always keep chat_id together with message_id because providers may only guarantee uniqueness inside the chat. Obtain with: provider read/list conversation messages -> message.id Never pass: message text, chat_id, message ID without its chat context for mutation tools.

Inputs: chat_id (required), message_id (required), account_id.

message_mark_readMessage: Mark readB
Destructive
Inspect

Mark one exact message read. Resolve chat_id then message_id; do not pass person/user ID as chat_id. Chat ID: Exact provider chat/conversation ID. LinkedIn chat IDs may also be visible in /messaging/thread/{chat_id}/ URLs. Obtain with: provider list conversations/inbox chats -> chat.id Never pass: person name, user_id, message_id. Message ID: Exact message id inside a specific chat. In V2 always keep chat_id together with message_id because providers may only guarantee uniqueness inside the chat. Obtain with: provider read/list conversation messages -> message.id Never pass: message text, chat_id, message ID without its chat context for mutation tools.

Inputs: chat_id (required), message_id (required), account_id.

message_remove_reactionMessage: Remove reactionA
Destructive
Inspect

Remove the user's reaction from one exact message. Resolve chat/message first. Chat ID: Exact provider chat/conversation ID. LinkedIn chat IDs may also be visible in /messaging/thread/{chat_id}/ URLs. Obtain with: provider list conversations/inbox chats -> chat.id Never pass: person name, user_id, message_id. Message ID: Exact message id inside a specific chat. In V2 always keep chat_id together with message_id because providers may only guarantee uniqueness inside the chat. Obtain with: provider read/list conversation messages -> message.id Never pass: message text, chat_id, message ID without its chat context for mutation tools.

Inputs: chat_id (required), reaction (required), message_id (required), account_id.

message_resolve_chatMessage: Resolve chatB
Read-onlyIdempotent
Inspect

List/search conversations so a human recipient/topic can be mapped to exact chat_id before reading/replying or resolving message_id. Do not use a person name as chat_id. For Facebook Pages use facebook_list_inboxes and facebook_list_inbox_chats to preserve Page identity. For LinkedIn use linkedin_list_inboxes then linkedin_list_inbox_chats because account-wide chat listing is not supported. Chat ID: Exact provider chat/conversation ID. LinkedIn chat IDs may also be visible in /messaging/thread/{chat_id}/ URLs. Obtain with: provider list conversations/inbox chats -> chat.id Never pass: person name, user_id, message_id.

Inputs: provider (required), limit, cursor, is_unread, +1 more.

message_send_native_mediaMessage: Send native mediaA
Destructive
Inspect

Send one media/file attachment using the provider's native rendering mode where supported. Resolve chat_id first. Provide padded base64 bytes; uploads use multipart when the complete JSON exceeds 1 MiB. Provider file limits still apply. Useful for inline image/video/native media; for WhatsApp multiple attachments may become separate provider messages, so this tool intentionally sends one attachment per call for predictable behavior.

Inputs: chat_id (required), filename (required), content_type (required), content_base64 (required), +2 more.

message_send_voice_noteMessage: Send voice noteA
Destructive
Inspect

Send an audio attachment as a native/playable voice note where the connected provider supports it (notably WhatsApp/Telegram). Resolve chat_id first. Provide padded base64 content + exact MIME type/filename. Uploads use multipart when the complete JSON exceeds 1 MiB; provider file limits still apply. Do not send the same voice note repeatedly after an uncertain timeout; read chat state first.

Inputs: chat_id (required), filename (required), content_type (required), content_base64 (required), +3 more.

messaging_find_chat_by_userMessaging: Find chat by userA
Read-onlyIdempotent
Inspect

Find the existing one-to-one chat for a known LinkedIn, WhatsApp, Instagram, Facebook or Telegram provider user ID. Use after resolving the user; user_id is not chat_id.

Inputs: user_id (required), account_id.

messaging_list_chatsMessaging: List chatsA
Read-onlyIdempotent
Inspect

List personal chats for WhatsApp, Instagram, Facebook or Telegram. For Facebook Pages use facebook_list_inboxes and facebook_list_inbox_chats; never fall back to the personal inbox. Chats are most recently active first; use it to find a chat_id. LinkedIn requires inbox-specific listing. V2 filters: type, before/after (on the chat's last activity), archived and unread; WhatsApp pages by offset, other providers by cursor. For 'messages received between X and Y' call messaging_list_recent_messages, which also reads the messages.

Inputs: provider (required), type, after, limit, +6 more.

messaging_list_messagesMessaging: List messagesA
Read-onlyIdempotent
Inspect

List messages in a known chat, newest first, with V2 filters/pagination (before/after on the message timestamp). Message IDs are scoped to their chat: keep chat_id for any later get/edit/delete/forward/reaction action.

Inputs: chat_id (required), after, limit, before, +4 more.

messaging_list_recent_messagesMessaging: List recent messagesA
Read-onlyIdempotent
Inspect

Digest of the messages RECEIVED across every WhatsApp/Instagram/Facebook/Telegram chat in a time window: 'what did I get on WhatsApp since yesterday noon?', 'summarize my Telegram messages of the last 2 hours', scheduled inbound digests. Enumerates chats without a creation-date filter, reads each one with message-level after/before and returns inbound messages grouped by chat, newest first. For Facebook, inbox_id selects one personal or Page inbox. When complete is false (enumeration or read limits, or unknown message direction), say so instead of presenting the digest as exhaustive. Returns chat_id + message id pairs usable with message_get / messaging_send_message.

Inputs: after (required), provider (required), chat_type (required), max_chats (required), +4 more.

messaging_resolve_recipientMessaging: Resolve recipientA
Read-onlyIdempotent
Inspect

Turn a person's name, nickname, phone number or handle into the exact WhatsApp/Instagram/Facebook/Telegram recipient BEFORE sending: searches the user's 1-to-1 chats (ranked by most recent exchange) and contacts. Returns incomplete (lookup could not be fully enumerated; do not send automatically), resolved (one clear match: send immediately with the recommended next tool, no extra confirmation needed when the user already gave the message), ambiguous (several people: ask which one, most recent conversation first) or not_found. Use for 'send a WhatsApp to Julien', 'reply to Marie on Instagram', 'message +33 6…'. Never pass a name as chat_id or user_id.

Inputs: name (required), provider (required), inbox_id, account_id.

messaging_send_messageMessaging: Send messageA
Destructive
Inspect

Send a message in an existing LinkedIn, WhatsApp, Instagram, Facebook or Telegram chat. Supports text, base64 file attachments and provider-specific options. Locate/read the chat first if chat_id is not already known. This is a real external send action.

Inputs: text (required), chat_id (required), specifics, account_id, +1 more.

messaging_send_to_contactMessaging: Send to contactA
Destructive
Inspect

One-step send for voice-style requests: 'send a WhatsApp to Julien saying I'm 10 minutes late'. Resolves the recipient like messaging_resolve_recipient and sends the text ONLY when exactly one person matches (existing conversation or contact). When lookup is incomplete or several people match, nothing is sent and the candidates are returned so you can ask the user which one. The user must have stated the message content; do not invent it.

Inputs: name (required), text (required), provider (required), inbox_id, +2 more.

messaging_set_chat_stateMessaging: Set chat stateB
Destructive
Inspect

Update supported chat state such as read/unread, archive/pin, label or mute metadata. Only send fields explicitly requested.

Inputs: chat_id (required), name, label, account_id, +4 more.

messaging_set_composingMessaging: Set composingA
Destructive
Inspect

Publish a typing or voice-recording composing signal in a known chat where supported (LinkedIn Classic, WhatsApp and Facebook). This is ephemeral provider state; use only when an agent workflow explicitly needs it.

Inputs: action (required), chat_id (required), account_id.

messaging_set_presenceMessaging: Set presenceA
Destructive
Inspect

Set the connected messaging account presence where the provider supports it (LinkedIn Classic, WhatsApp, Telegram; Facebook: online/offline only). Use only for an explicit presence request.

Inputs: presence (required), account_id.

messaging_start_chatMessaging: Start chatA
Destructive
Inspect

Start a new personal WhatsApp, Instagram, Facebook or Telegram one-to-one/group chat (Facebook Pages cannot start chats) by sending its first message. Resolve users_ids first. A string starts 1-to-1; an array requests a group. LinkedIn requires the inbox-specific start tool.

Inputs: text (required), provider (required), users_ids (required), name, +3 more.

social_delete_commentPosts: Delete commentA
Destructive
Inspect

Delete one exact comment. Resolve post_id then comment_id; never use comment text as ID. Destructive. Post ID: Exact provider post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it. Comment ID: Exact comment id scoped to the identified post. Obtain with: linkedin_list_post_comments(post_id) -> comment.id; instagram_list_post_comments(post_id) -> comment.id Never pass: comment text, post_id.

Inputs: post_id (required), comment_id (required), account_id.

social_delete_postPosts: Delete postA
Destructive
Inspect

Delete an exact supported social post. Resolve/verify post_id first. Destructive: explicit deletion intent required. Post ID: Exact provider post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it.

Inputs: post_id (required), account_id.

social_list_comment_reactionsPosts: List comment reactionsA
Read-onlyIdempotent
Inspect

List detailed reactions on an exact comment. First resolve post_id, then list comments and select comment.id. Post ID: Exact provider post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it. Comment ID: Exact comment id scoped to the identified post. Obtain with: linkedin_list_post_comments(post_id) -> comment.id; instagram_list_post_comments(post_id) -> comment.id Never pass: comment text, post_id.

Inputs: post_id (required), comment_id (required), offset, account_id.

social_react_to_commentPosts: React to commentA
Destructive
Inspect

Like/react to one exact comment as the connected person. For a LinkedIn company page, set react_as from linkedin_list_managed_company_pages on the same account. Confirm the action and target identity. Resolve post -> comment before acting. Do not confuse post_id and comment_id. Post ID: Exact provider post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it. Comment ID: Exact comment id scoped to the identified post. Obtain with: linkedin_list_post_comments(post_id) -> comment.id; instagram_list_post_comments(post_id) -> comment.id Never pass: comment text, post_id.

Inputs: post_id (required), reaction (required), comment_id (required), react_as, +1 more.

social_remove_comment_reactionPosts: Remove comment reactionA
Destructive
Inspect

Remove the user's reaction from one exact comment. Resolve post_id/comment_id first. Post ID: Exact provider post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it. Comment ID: Exact comment id scoped to the identified post. Obtain with: linkedin_list_post_comments(post_id) -> comment.id; instagram_list_post_comments(post_id) -> comment.id Never pass: comment text, post_id.

Inputs: post_id (required), reaction (required), comment_id (required), account_id.

social_remove_post_reactionPosts: Remove post reactionA
Destructive
Inspect

Remove the user's reaction from one exact post. Resolve post_id first; never use post URL/text unless another resolver explicitly converts it. Post ID: Exact provider post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it.

Inputs: post_id (required), reaction (required), account_id.

social_resolve_commentPosts: Resolve commentB
Read-onlyIdempotent
Inspect

List comments for an already-resolved post so the agent can map a human reference such as 'the comment from Sarah' to exact comment_id before replying/reacting/editing/deleting. First resolve post_id. Post ID: Exact provider post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it. Comment ID: Exact comment id scoped to the identified post. Obtain with: linkedin_list_post_comments(post_id) -> comment.id; instagram_list_post_comments(post_id) -> comment.id Never pass: comment text, post_id.

Inputs: post_id (required), cursor, offset, account_id.

social_update_commentPosts: Update commentA
Destructive
Inspect

Edit an existing comment. Required chain when starting from human text: resolve post -> post.id -> list comments -> comment.id -> edit. post_id and comment_id are different ID namespaces. Post ID: Exact provider post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it. Comment ID: Exact comment id scoped to the identified post. Obtain with: linkedin_list_post_comments(post_id) -> comment.id; instagram_list_post_comments(post_id) -> comment.id Never pass: comment text, post_id.

Inputs: text (required), post_id (required), comment_id (required), account_id.

social_update_postPosts: Update postA
Destructive
Inspect

Edit an existing supported social post. Resolve the exact post first, then reuse post.id. Never infer an ID from post text or author. Post ID: Exact provider post id; LinkedIn commonly uses a preformatted/base64-style post ID. Obtain with: linkedin_search_posts -> result.id; linkedin_list_user_posts -> result.id; instagram_list_user_posts -> result.id Never pass: post text, author user ID, URL unless a resolver tool explicitly accepts it.

Inputs: post_id (required), text, account_id, can_comment.

team_add_seatsTeam: Add seatsA
Destructive
Inspect

Add (or reduce) paid extra seats on the Team subscription so more colleagues can be invited. Billing owner only; prorated immediately on the saved payment method. FIRST call without confirm to get the price and a one-click Stripe confirmation link, then call with confirm=true after the user approves. extra_seats is the ADDED number of seats relative to the current paid extra seats (use 1 to add one seat).

Inputs: extra_seats (required), confirm.

team_invite_memberTeam: Invite memberA
Destructive
Inspect

Invite a colleague to the user's Team workspace by email. Each member gets a separate login, isolated provider Scope and their own connected accounts; the team only centralizes billing and seats. Only team owners/admins can invite. When no seat is free, the result explains how to add a paid seat (team_add_seats). If the user is not on Team, propose account_change_plan(plan='team').

Inputs: email (required).

telegram_connectTelegram: ConnectA
Destructive
Inspect

Connect or reconnect the user's Telegram account directly in the conversation: returns a QR code image to scan from Telegram > Settings > Devices > Link Desktop Device, then poll account_connection_status until connected. Accounts protected by a Telegram cloud password (2FA) must use the browser link returned by account_connect instead. Use account_id to re-authenticate an existing disconnected Telegram account.

Inputs: account_id.

webhook_create_destinationRealtime: Create destinationA
Destructive
Inspect

Create a realtime event destination for this Nilyo user. Nilyo creates the endpoint server-side but ALWAYS restricts it to account IDs owned by this authenticated user. By default matching future accounts are automatically added. Explicit account_ids without a providers filter stay restricted to those accounts, even with auto_include_new_accounts=true. For n8n use its Test URL first, validate with a Development/Mock event, then update to Production URL. The endpoint signing secret is kept encrypted server-side and is never returned by MCP: never ask for it.

Inputs: name (required), events (required), runtime (required), request_url (required), +3 more.

webhook_delete_destinationRealtime: Delete destinationA
Destructive
Inspect

Delete an Nilyo-owned webhook endpoint. This stops future realtime delivery to that destination; require explicit user intent.

Inputs: destination_id (required).

webhook_get_delivery_logsRealtime: Get delivery logsA
Read-onlyIdempotent
Inspect

Inspect recent webhook delivery attempts for this destination. Use when an agent/n8n receiver did not wake or a test event was not observed. Use to investigate whether a delivery was attempted.

Inputs: limit (required), destination_id (required).

webhook_get_destinationRealtime: Get destinationB
Read-onlyIdempotent
Inspect

Get one Nilyo-owned webhook destination and its configured events/provider/account selection.

Inputs: destination_id (required).

webhook_get_setup_guideRealtime: Get setup guideA
Read-onlyIdempotent
Inspect

Get runtime-specific instructions for receiving realtime events in n8n, OpenClaw, Hermes, Make or a generic agent. Use BEFORE creating the webhook when the user has not yet produced a public receiver URL.

Inputs: runtime (required).

webhook_get_test_guideRealtime: Get test guideA
Read-onlyIdempotent
Inspect

Return the exact test procedure for a destination. Generate a mock/test event with a Mock account (Test & Debug), then inspect webhook_get_delivery_logs and the target runtime. Nilyo does not fabricate provider event payloads because the mock event is the source of truth.

Inputs: destination_id (required).

webhook_list_available_eventsRealtime: List available eventsA
Read-onlyIdempotent
Inspect

List realtime event types Nilyo can subscribe an agent to, plus the common event envelope. Use this before creating a destination if the user's requested trigger is ambiguous.

Inputs: no named parameters.

webhook_list_destinationsRealtime: List destinationsA
Read-onlyIdempotent
Inspect

List webhook destinations created by this Nilyo user. These are control-plane records; realtime events are delivered directly to the destination, not relayed through Nilyo.

Inputs: no named parameters.

webhook_update_destinationRealtime: Update destinationA
Destructive
Inspect

Update a webhook destination URL, events or provider/account selection. Common n8n chain: create with Test URL -> receive mock event -> update same destination to Production URL. Nilyo recomputes authorized account_ids server-side.

Inputs: destination_id (required), name, events, enabled, +5 more.

whatsapp_connectWhatsApp: ConnectA
Destructive
Inspect

Connect or reconnect the user's WhatsApp account directly in the conversation without leaving the agent. Default mode returns a QR code image to scan from WhatsApp > Linked devices; with phone_number it returns a pairing code to type on the phone instead (useful when the QR image cannot be displayed). Then poll account_connection_status until connected. Requires an active trial/subscription and a free WhatsApp slot on the plan; otherwise the result explains the upgrade. Use account_id to re-authenticate an existing disconnected WhatsApp account.

Inputs: account_id, phone_number.

whatsapp_get_profileWhatsApp: Get profileA
Read-onlyIdempotent
Inspect

Retrieve a WhatsApp user profile by provider user ID or supported phone-number identifier. Use to resolve/verify the recipient before a new chat.

Inputs: user_id (required), account_id.

whatsapp_is_number_registeredWhatsApp: Is number registeredA
Read-onlyIdempotent
Inspect

Check whether a phone number corresponds to a WhatsApp user/account before starting outreach or resolving a WhatsApp recipient. Pass the number in international form.

Inputs: phone_number (required), account_id.

whatsapp_list_contactsWhatsApp: List contactsA
Read-onlyIdempotent
Inspect

List WhatsApp contacts so a human name/phone can be resolved to an exact provider user identity before starting a new chat. Reuse the returned provider user ID; do not pass display name as whatsapp_user_id.

Inputs: limit, cursor, offset, account_id.

whatsapp_list_conversationsWhatsApp: List conversationsA
Read-onlyIdempotent
Inspect

List WhatsApp chats from the user's own connected WhatsApp account, most recently active first. Use to find a chat_id before reading or sending when the user identifies a conversation by person/name rather than ID. For 'what did I receive since X' use messaging_list_recent_messages.

Inputs: limit, account_id.

whatsapp_read_conversationWhatsApp: Read conversationA
Read-onlyIdempotent
Inspect

Read a WhatsApp chat and recent message history. Use for context, summaries, follow-up detection and cross-channel workflows before sending a reply.

Inputs: chat_id (required), account_id.

whatsapp_send_messageWhatsApp: Send messageA
Destructive
Inspect

Send a WhatsApp message in an existing chat from the user's own account. If chat_id is unknown, call whatsapp_list_conversations first. Use only after the final message is explicitly requested/approved.

Inputs: text (required), chat_id (required), account_id.

whatsapp_start_conversationWhatsApp: Start conversationA
Destructive
Inspect

Start a new 1-to-1 WhatsApp chat and send the first message. Resolve/verify recipient first with whatsapp_list_contacts or WhatsApp profile/number lookup. whatsapp_user_id must be provider identity, never a contact display name.

Inputs: text (required), whatsapp_user_id (required), account_id.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to read and manage conversations across LinkedIn, WhatsApp, Telegram, and Instagram, research profiles, draft replies, and carry out user-approved messaging, invitations, posts, and outreach.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to discover, write, and test integrations for LinkedIn (Classic, Sales Navigator, Recruiter), WhatsApp, Instagram, Telegram, Gmail/Outlook/IMAP email, and Google/Outlook calendar by reading the live API contract and executing real calls on connected accounts.
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to access LinkedIn for lead search, messaging, outreach campaigns, and content management, with activity limits and optional warm-up.
      53 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage social media accounts and CRM operations, including posting, analytics, inbox management, and customer management.
      22
      Apache 2.0
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.