Reach MCP

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. Changes limits and the activity window for jobs; does not reset today's counters. Raising a limit is the user's decision, ask first.

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

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and idempotentHint=true, so safety/idempotency are covered structurally. The description adds real behavioral context beyond them: partial-update semantics, that it does not reset today's counters, and a consent rule for raising limits. It stops short of describing the response or failure modes, so not a 5.

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

Conciseness5/5

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

Four tight sentences, zero filler, with the core scope front-loaded and the consent caveat last. Every sentence carries actionable information.

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

Completeness5/5

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

For a 15-parameter mutation with full schema coverage and an output schema (so return values need not be explained), the description covers scope, partial-update behavior, side-effect boundaries, and a consent rule. Nothing essential to correct invocation is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already documents all 15 parameters (baseline 3). The description adds genuine meaning by framing the window params as an inheritance default (used when a job does not set its own), which the schema does not state.

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

Purpose5/5

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

States a specific verb (update) and resource (quota configuration fields plus activity window for a LinkedIn account), and distinguishes itself from get_account_quotas by being the mutating counterpart. An agent can identify the operation without opening the schema.

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

Usage Guidelines4/5

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

Gives clear operating context: only provided fields are updated (partial update), changes apply to jobs rather than today's counters, and raising a limit requires asking the user first. It does not explicitly name the alternative tool (get_account_quotas) or state when-not to use this, so it falls short of a 5.

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

All Reach MCP 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?