> ## Documentation Index
> Fetch the complete documentation index at: https://docs.linkedcamp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Account settings

> Notifications, your own profile preferences, and the team roster.

| Tool | Kind |
| - | - |
| [`account_settings_update`](#account_settings_update) | Write |
| [`help_videos`](#help_videos) | Read-only |
| [`notification_list`](#notification_list) | Read-only |
| [`notification_mark_read`](#notification_mark_read) | Write |
| [`team_members_list`](#team_members_list) | Read-only |

## account\_settings\_update

<Badge color="orange">Write</Badge>

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

<ParamField path="firstName" type="string">
  Given name.
</ParamField>

<ParamField path="lastName" type="string">
  Family name.
</ParamField>

<ParamField path="language" type="string">
  UI language code, e.g. "en", "fr", "de", "it", "pt", "ja".
</ParamField>

<ParamField path="settings" type="object">
  Inbox, reporting and notification toggles.

  <Expandable title="properties">
    <ParamField path="inboxManager" type="boolean">
      Let the AI assistant triage the unibox.
    </ParamField>

    <ParamField path="suggestReplies" type="boolean">
      Stored preference for AI reply suggestions in the inbox. No current web-app screen exposes it.
    </ParamField>

    <ParamField path="sentimentAnalysis" type="boolean">
      Auto-classify replies as positive/negative/neutral.
    </ParamField>

    <ParamField path="tagId" type="string">
      Tag applied automatically to positive replies.
    </ParamField>

    <ParamField path="addToBlacklist" type="boolean">
      Blacklist a lead automatically when they opt out.
    </ParamField>

    <ParamField path="notifyLowProspects" type="boolean">
      Email you when a campaign is running out of leads.
    </ParamField>

    <ParamField path="notifyLIDisconnection" type="boolean">
      Email you when a LinkedIn session expires.
    </ParamField>

    <ParamField path="notifyEmailDisconnection" type="boolean">
      Email you when a mailbox stops sending.
    </ParamField>

    <ParamField path="notifyPositiveReply" type="boolean">
      Email you whenever a lead replies positively.
    </ParamField>

    <ParamField path="dailyReport" type="boolean">
      One email each morning summarising yesterday's outreach.
    </ParamField>

    <ParamField path="weeklyReport" type="boolean">
      One email each Monday summarising the previous week.
    </ParamField>
  </Expandable>
</ParamField>

## help\_videos

<Badge color="blue">Read-only</Badge>

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

<Badge color="blue">Read-only</Badge>

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

<Badge color="orange">Write</Badge>

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

<ParamField path="notificationId" type="string">
  Notification id, from `notification_list`. Omit to act on all of them.
</ParamField>

## team\_members\_list

<Badge color="blue">Read-only</Badge>

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.*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.