Skip to main content
Glama

LinkedIn: List managed company pages

linkedin_list_managed_company_pages
Read-onlyIdempotent

Discover the LinkedIn company pages this connected account administers. Reuse the selected data[].id (NOT mailbox_id) with the SAME account_id as post_as for linkedin_create_post, comment_as for linkedin_comment_on_post/linkedin_reply_to_comment, or react_as for linkedin_react_to_post/social_react_to_comment. Requires the company product selected in Hosted Auth; if access is refused, reconnect the SAME account with account_connect and select Company Pages. A company search result does not prove admin rights; never fall back to acting as the person.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "linkedin_list_managed_company_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare this as a read-only, idempotent, non-destructive operation. The description adds important behavioral context beyond annotations: Hosted Auth must include the company product, access failures require reconnecting the same account, and mailbox_id must not be used as the page ID.

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?

The purpose is front-loaded, and each sentence carries operational value: ID reuse, auth prerequisites, recovery steps, and a clear warning against false admin assumptions. There is no filler.

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 one-optional-parameter read-only tool with no output schema, the description supplies the missing output context (data[].id versus mailbox_id), auth requirements, downstream usage, and failure handling. An agent has enough information to call it correctly and interpret the result.

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?

The single account_id parameter is fully described in the schema, so the baseline is moderate. The description adds useful semantics by requiring the SAME account_id used by downstream posting, commenting, and reacting actions, linking the parameter to cross-tool consistency.

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: discover LinkedIn company pages administered by the connected account. It also distinguishes admin-managed pages from ordinary company search results, so an agent can tell what this tool is for.

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 tells the agent to reuse the returned page ID for post_as, comment_as, or react_as with the same account_id. It also gives when-not guidance: a company search result does not prove admin rights and the agent must not fall back to acting as the person.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.