Reach MCP — LinkedIn for AI agents

get_account_quotas

Read-onlyIdempotent

Get the quotas configuration and usage counters for a LinkedIn account.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON 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_imports_salesnav_conf`	No
`daily_imports_salesnav_used`	No
`daily_imports_standard_conf`	No
`daily_imports_standard_used`	No
`daily_imports_recruiter_conf`	No
`daily_imports_recruiter_used`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds only that both configuration and usage counters are returned, which is also implied by the output schema, so it contributes little extra behavioral context.

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?

One clean sentence, front-loaded with the verb and resource, with no redundant or filler text.

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?

For a single-parameter read tool with full annotation coverage and an output schema, the description covers what is needed to call it correctly. Only minor gaps remain, such as noting the account_id source or the relationship to quota-update operations.

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% and the single parameter (account_id) is already documented as a Reach id sourced from list_accounts. The description adds no syntax, format, or sourcing detail beyond the schema, so the baseline 3 applies.

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 (Get) and resource (quotas configuration and usage counters) scoped to a LinkedIn account, which distinguishes it from most siblings. It does not explicitly name its closest counterpart, update_account_quotas, but the read/write distinction is implied by 'Get'.

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?

Usage is implied by the name and verb – fetch quota state for an account – but there is no explicit when-to-use guidance, no mention of the list_accounts prerequisite, and no contrast with update_account_quotas or the log/stats siblings.

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?