Skip to main content

​
account_settings_update

Write Update your own profile and notification preferences: name, language, and the inbox-manager / reporting / notification toggles. Billing details, password and email are intentionally not writable over MCP. Your own user profile only. It does not touch a LinkedIn account’s settings (linkedin_account_update), a mailbox’s (email_account_update), or anything on a campaign (campaign_update). Billing, team management and tenant configuration are outside this server entirely.

​
Parameters

​
string
Given name.
​
string
Family name.
​
string
UI language code, e.g. “en”, “fr”, “de”, “it”, “pt”, “ja”.
​
object
Preference toggles.

​
help_videos

Read-only Product walkthrough videos, for linking a user to the right explainer. Reach for it when the answer is a web-app action with no tool — connecting a LinkedIn account, pausing a campaign, billing — so the user is pointed somewhere useful rather than told no. Links only; it changes nothing and reads no account data, unlike whoami or notification_list. No parameters.

​
notification_list

Read-only In-app notifications: disconnected accounts, campaigns running low on prospects, positive replies, limits hit. The platform telling you something needs attention — worth reading when diagnosing why a campaign stopped. These are not prospect replies (conversation_list) and not to-dos (task_list). Clear the badge with notification_mark_read; there is no tool to delete a notification. No parameters.

​
notification_mark_read

Write Mark one notification read, or all of them if notificationId is omitted — so omitting it clears the whole badge, which is worth confirming first. It only changes read state; the notification is kept, and deleting one is not available. For inbox threads use conversation_update or conversation_mark_all_read instead.

​
Parameters

​
string
Notification id, from notification_list. Omit to act on all of them.

​
team_members_list

Read-only People with access to this account and their roles. Read-only — inviting and removing members is not exposed over MCP, and neither is changing a role. Useful for reading a userId before an owner-only call such as campaign_list or agent_duplicate for a sub-account. Those arguments are accepted only from an account owner. No parameters.