Actions

Call the updateAccountLimits MCP tool

Update a LinkedIn account’s daily limits and/or its working-hours send window - two independent things, do not confuse them. daily_limits_schedule is per-weekday invite COUNTS (how many invites go out each weekday). working_hours_timezone / working_hours_schedule / working_hours_enabled control the send WINDOW (what clock hours sends are allowed to happen in at all) - a completely different axis, stored separately. Editable: connection_request_limit (0-25), reply_agent_daily_cap (0-100), daily_limits_schedule (per-weekday invite caps; see its field description for the required shape), working_hours_timezone (IANA string), working_hours_schedule (per-weekday send window; see its field description), working_hours_enabled (turn the window on/off without discarding it). message_limit and profile_lookup_limit are fixed platform defaults and cannot be changed. Partial update: send only the fields you are changing; every omitted field is preserved, including across the limits/working-hours split (sending only working-hours fields never touches limits, and vice versa).

Called through the Actions bridge: the response is that tool's own result, wrapped as { data: <tool result> } under HTTP 200. Billing, daily-cap, and confirm-step outcomes are embedded INSIDE data, never remapped to an HTTP status (see the templated /api/v1/actions/{toolName} operation above for the full protocol, and x-mcp-actions for this tool's machine-readable scope/cap/confirm_behavior fields). Authentication, request-shape, and optional idempotency-protocol failures still use their documented non-200 statuses.

post/api/v1/actions/updateAccountLimits

Request

  • Base URL: https://app.reachium.io
  • URL: https://app.reachium.io/api/v1/actions/updateAccountLimits
  • Auth: HTTP bearer

Headers

Idempotency-Keystring

Optional caller-generated key (8-200 characters: letters, digits, dot, underscore, colon, or hyphen). A final tool result is replayed for the same key and body. An ambiguous result remains 409 under that key; reconcile external state before using a new key. Reuse with a different body returns 422.

Request body

account_idstring uuid required

The LinkedIn account (from getLinkedInAccounts).

connection_request_limitinteger

Daily connection-request cap, 0-25.

reply_agent_daily_capinteger

Optional daily cap for the auto reply-agent, 0-100.

daily_limits_scheduleobject nullable

Per-weekday invite COUNTS. ALL 7 keys "0"-"6" required, each 0-100, weekly total <= 200. null clears it. NOT the send-hours window - see working_hours_schedule for that.

working_hours_timezonestring

IANA timezone for the working-hours window (e.g. "America/New_York"). Independent of daily_limits_schedule.

working_hours_scheduleobject nullable

Per-weekday send-hours WINDOW (not invite counts - see daily_limits_schedule for those). ALL 7 keys "0" (Sunday) through "6" (Saturday) required - this is a full replace of the week, and a missing day is treated as CLOSED, so a partial object would silently stop sends on the days you leave out. Call getAccountLimits first to read the current window, then send back all 7 days (change only the ones you mean to change). Value per day is { start, end } as 4-digit UTC clock time (HHMM, 0-2359) or null for "closed that day". A window may wrap UTC midnight, e.g. start: 1600, end: 400 for an overnight schedule - that is valid, not an error. null the WHOLE field (not a per-day value) to remove all window restrictions (account sends any hour, matching working_hours_enabled: false).

working_hours_enabledboolean

Turn the working-hours window on/off without discarding working_hours_schedule.

Response

The result of calling this tool.

dataunknown required
errorunknown required

Changes

No recorded changes to this operation across all 2 revisions of this API.