Reach MCP — LinkedIn for AI agents

update_account_quotas

Idempotent

Update one or more quota configuration fields for a LinkedIn account, and its activity window (the hours, days and timezone jobs run in when a job does not set its own). Only provided fields are updated.

Input Schema

TableJSON Schema

Name	Required	Description
`timezone`	No	IANA zone for the window, e.g. Europe/Paris. Empty string resets to the zone of the account's proxy country.
`account_id`	Yes	Reach id of the LinkedIn account to act on, from list_accounts.
`window_end`	No	HH:MM: jobs on this account stop at this time. Empty string resets to 18:00.
`window_days`	No	Weekdays jobs may run: mon, tue, wed, thu, fri, sat, sun. Empty list resets to Monday–Friday.
`window_start`	No	HH:MM, in the account's timezone: jobs on this account start no earlier. Empty string resets to 09:00.
`idempotency_key`	No	Optional. A key you choose (a UUID is fine) that names this exact call. If you retry with the same key and the same arguments, the first call's result is returned and nothing is done twice on LinkedIn. Reusing a key with different arguments is refused. Keys expire after 24 hours.
`daily_posts_conf`	No	Daily limit for 'posts' on this account; 0 means unlimited.
`daily_visits_conf`	No	Daily limit for 'visits' on this account; 0 means unlimited.
`daily_comments_conf`	No	Daily limit for 'comments' on this account; 0 means unlimited.
`daily_messages_conf`	No	Daily limit for 'messages' on this account; 0 means unlimited.
`daily_reactions_conf`	No	Daily limit for 'reactions' on this account; 0 means unlimited.
`daily_invitations_conf`	No	Daily limit for 'invitations' on this account; 0 means unlimited.
`daily_imports_salesnav_conf`	No	Daily limit for 'imports_salesnav' on this account; 0 means unlimited.
`daily_imports_standard_conf`	No	Daily limit for 'imports_standard' on this account; 0 means unlimited.
`daily_imports_recruiter_conf`	No	Daily limit for 'imports_recruiter' on this account; 0 means unlimited.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`quotas`	No
`window`	No
`updated`	No
`account_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 27, 2026

addedInput schema / properties / timezone

Added value: +{
+  "description": "IANA zone for the window, e.g. Europe/Paris. Empty string resets to the zone of the account's proxy country.",
+  "type": "string"
+}

addedInput schema / properties / window_days

Added value: +{
+  "description": "Weekdays jobs may run: mon, tue, wed, thu, fri, sat, sun. Empty list resets to Monday–Friday.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / window_end

Added value: +{
+  "description": "HH:MM: jobs on this account stop at this time. Empty string resets to 18:00.",
+  "type": "string"
+}

addedInput schema / properties / window_start

Added value: +{
+  "description": "HH:MM, in the account's timezone: jobs on this account start no earlier. Empty string resets to 09:00.",
+  "type": "string"
+}

addedOutput schema / properties / window

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedSep 10, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds the partial-update contract ('only provided fields are updated') and frames the activity-window semantics, but says nothing about permissions, immediate effect, or interaction with running jobs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence that front-loads the primary action (quota fields) before the secondary scope (activity window) and closes with the update rule. No wasted text, though the embedded parenthetical definition is slightly dense.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 15 parameters, a full output schema and solid annotations, the description covers the two facets of the tool adequately. It still omits when changes take effect, how they affect in-flight or scheduled jobs, and where to read current quotas, which an agent would want for a mutation of this size.

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

Parameters3/5

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

Schema description coverage is 100%, including reset semantics for empty values and the idempotency key contract, so the schema does the heavy lifting. The description's only added meaning is the blanket 'only provided fields are updated' rule, which is baseline-level value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource ('Update one or more quota configuration fields for a LinkedIn account') and extends the scope to the activity window, which the name alone would not convey. It does not explicitly name the sibling read tool get_account_quotas, so sibling differentiation is left to the verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Only provided fields are updated' gives a useful sparse-update rule, but there is no explicit when-to-use guidance or pointer to get_account_quotas for inspecting current values before/after mutating them. Usage is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Reach MCP — LinkedIn for AI agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?