Reach MCP — LinkedIn for AI agents

list_managed_pages

Read-onlyIdempotent

List the LinkedIn company pages the account administers: page_id, name, URL, the account's admin roles, what those roles allow (post, comment, react, delete_post, read_messages, send_messages, read_activity) and whether page messaging is on. Pass a page_id to create_post, upload_media_from_url, create_multi_photo, comment_post, reply_comment or like_post to act as that page instead of the member, to list_conversations, list_conversation_messages or send_message for the page inbox, and to list_page_activity for the comments and mentions it received. Use when the user wants to act as a company page (post, comment, like as the page) to get its page_id and check the role allows it; empty when the account administers no page. Cached ten minutes. Read-only.

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": "list_managed_pages"
  }
}

Input Schema

Name	Required	Description	Default
`refresh`	No	Re-read the pages from LinkedIn instead of the 10-minute cache (after a role change).
`account_id`	Yes	Reach id of the LinkedIn account to act on, from list_accounts.

Output Schema

Name	Required	Description	Default
`pages`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026
- addedOutput schema / properties / pages / items / properties / permissions / properties / read_analytics
```
Added value: +{
+  "type": "boolean"
+}
```
AddedNov 3, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: the ten-minute cache, the refresh behavior after a role change, the empty-result case, and the exact capability flags returned for each role. The read-only nature is consistent with readOnlyHint=true and destructiveHint=false.

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?

The definition is dense but front-loaded: it first states what is returned, then explains how page_id is used, then gives the use case and caching behavior. It is somewhat long and includes a final 'Read-only' restatement already covered by annotations, but nearly 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?

Given the tool's role as a page-discovery prerequisite for many page-acting siblings, the description covers output fields, role capabilities, downstream usage, caching, refresh, and the empty case. An output schema exists, so return-value structure need not be further explained.

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 parameter definitions are already documented. The description still adds useful meaning by explaining that page_id is the actor selector for create_post, upload_media_from_url, create_multi_photo, comment_post, reply_comment, like_post, the page inbox tools, and list_page_activity.

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 ('List the LinkedIn company pages the account administers') and enumerates the returned fields, including admin roles, role capabilities, and page messaging status. It clearly distinguishes this discovery tool from sibling action tools that consume page_id.

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?

Explicitly says when to use it: when acting as a company page to obtain its page_id and check that the role permits the intended action. It names the exact downstream tools for posting, commenting, reacting, messaging, and activity retrieval, and notes that the result is empty when no page is administered.

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?