Reach MCP — LinkedIn for AI agents

get_account_quotas

Read-onlyIdempotent

Get the quotas configuration and usage counters for a LinkedIn account. Use before a batch to know what is left today; use update_account_quotas to change limits or the activity window.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account_id": "<account_id>"
    },
    "name": "get_account_quotas"
  }
}

Input Schema

Name	Required	Description	Default
`account_id`	Yes	Reach id of the LinkedIn account to act on, from list_accounts.

Output Schema

Name	Required	Description
`id`	No
`window`	No	The activity window jobs run in by default.
`timezone`	No
`window_end`	No
`window_days`	No
`window_start`	No
`daily_posts_conf`	No
`daily_posts_used`	No
`daily_visits_conf`	No
`daily_visits_used`	No
`daily_comments_conf`	No
`daily_comments_used`	No
`daily_messages_conf`	No
`daily_messages_used`	No
`daily_reactions_conf`	No
`daily_reactions_used`	No
`daily_invitations_conf`	No
`daily_invitations_used`	No
`daily_job_searches_conf`	No
`daily_job_searches_used`	No
`daily_messaging_reads_conf`	No
`daily_messaging_reads_used`	No
`daily_imports_salesnav_conf`	No
`daily_imports_salesnav_used`	No
`daily_imports_standard_conf`	No
`daily_imports_standard_used`	No
`daily_linkedin_requests_max`	No
`daily_imports_recruiter_conf`	No
`daily_imports_recruiter_used`	No
`daily_linkedin_requests_conf`	No
`daily_linkedin_requests_used`	No
`messaging_min_interval_seconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 8, 2026

addedOutput schema / properties / daily_job_searches_conf

Added value: +{
+  "title": "Daily Job Searches Conf",
+  "type": "integer"
+}

addedOutput schema / properties / daily_job_searches_used

Added value: +{
+  "title": "Daily Job Searches Used",
+  "type": "integer"
+}

Changed6 schema fields changedOct 8, 2026

addedOutput schema / properties / daily_linkedin_requests_conf

Added value: +{
+  "title": "Daily Linkedin Requests Conf",
+  "type": "integer"
+}

addedOutput schema / properties / daily_linkedin_requests_max

Added value: +{
+  "title": "Daily Linkedin Requests Max",
+  "type": "integer"
+}

addedOutput schema / properties / daily_linkedin_requests_used

Added value: +{
+  "default": 0,
+  "title": "Daily Linkedin Requests Used",
+  "type": "integer"
+}

addedOutput schema / properties / daily_messaging_reads_conf

Added value: +{
+  "title": "Daily Messaging Reads Conf",
+  "type": "integer"
+}

addedOutput schema / properties / daily_messaging_reads_used

Added value: +{
+  "default": 0,
+  "title": "Daily Messaging Reads Used",
+  "type": "integer"
+}

addedOutput schema / properties / messaging_min_interval_seconds

Added value: +{
+  "title": "Messaging Min Interval Seconds",
+  "type": "integer"
+}

Changed6 schema fields changedSep 27, 2026

addedOutput schema / properties / timezone

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Timezone"
+}

addedOutput schema / properties / window

Added value: +{
+  "additionalProperties": true,
+  "description": "The activity window jobs run in by default.",
+  "properties": {
+    "customised": {
+      "type": "boolean"
+    },
+    "days": {
+      "items": {
+        "type": "integer"
+      },
+      "type": "array"
+    },
+    "timezone": {
+      "type": "string"
+    },
+    "window_end": {
+      "type": "string"
+    },
+    "window_start": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / window_days

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "integer"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Window Days"
+}

addedOutput schema / properties / window_end

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Window End"
+}

addedOutput schema / properties / window_start

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Window Start"
+}

removedOutput schema / title
```
Removed value: -"QuotasOut"
```

First observedSep 10, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds only that it surfaces usage counters and today's remaining budget; it says nothing about rate limits, auth requirements, or behavior for accounts without quotas.

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?

Two sentences, zero padding, with the purpose front-loaded and the sibling routing placed after the usage hint. Every clause earns its place.

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

Completeness4/5

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

An output schema exists, so return values need no explanation, and the description covers purpose, timing, and the mutation alternative. Minor gaps remain around error/empty-quota behavior, but nothing essential for correct invocation is missing.

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?

Single parameter with 100% schema description coverage, including provenance ('from list_accounts'). The description adds no syntax or format detail beyond the schema, so the baseline 3 for high coverage applies.

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 and resource ('Get the quotas configuration and usage counters for a LinkedIn account'), and explicitly names the related sibling (update_account_quotas) so the agent can distinguish reading quotas from mutating them.

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

Usage Guidelines5/5

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

Gives concrete when-to-use guidance ('Use before a batch to know what is left today') and routes the alternative case to update_account_quotas for changing limits or the activity window. Both usage and the exclusion are explicit.

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?