Skip to main content
Glama

fetch_company

Retrieve a company's basic information from LinkedIn. Optionally gather its employees, posts, and decision makers as well.

Instructions

Allows you to open a company page to retrieve its basic information (st.openCompanyPage action). Can optionally retrieve employees, posts and decision makers.

Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work.

A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyUrlYesPublic or hashed LinkedIn URL of the company. (e.g., 'https://www.linkedin.com/company/microsoft')
retrieveDMsNoOptional. Whether to retrieve the company's decision makers information. Default is false.
retrievePostsNoOptional. Whether to retrieve the company's posts information. Default is false.
retrieveEmployeesNoOptional. Whether to retrieve the company's employees information. Default is false.
dmsRetrievalConfigNoOptional. Configuration for retrieving decision makers. Available only if retrieveDMs is true.
postsRetrievalConfigNoOptional. Configuration for retrieving posts. Available only if retrievePosts is true.
employeesRetrievalConfigNoOptional. Configuration for retrieving employees. Available only if retrieveEmployees is true.
Behavior5/5

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

With no annotations, the description fully discloses the asynchronous behavior: immediate pending response, long-polling via get_workflow_result, duplicate-work risk on retries, and detailed explanation of pendingReason states including 'queued' and 'outsideWorkingHours'. This goes far beyond basic mutation/read hints and provides critical usage context.

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 description is three paragraphs, but each section earns its place: purpose, workflow mechanics, and edge-case handling. It is somewhat lengthy but not wasteful; the detail is necessary for correct asynchronous usage. The structure is logical and front-loaded with the core purpose.

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?

Given the complexity of the async workflow and nested parameters, the description thoroughly explains the immediate response, how to retrieve results, and how to handle pending states. However, it does not describe the final result structure (no output schema), though the name and purpose imply the content. Overall comprehensive for a complex tool.

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%, so the baseline is 3. The description only briefly mentions optional retrieval of employees, posts, and decision makers, but the input schema already provides detailed semantics for each parameter, including limits and filters. The description adds minimal new parameter-level meaning beyond the schema.

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?

The description explicitly states that the tool opens a company page and retrieves basic information, with optional retrieval of employees, posts, and decision makers. It clearly identifies the resource (company) and action (fetch), distinguishing it from sibling tools like fetch_person or search_companies.

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?

The description provides clear operational guidance on the asynchronous workflow, instructing the agent to call get_workflow_result with the returned workflowId and operationName, and explicitly warns against retrying the original tool while a workflow is running. However, it does not explicitly compare to alternative tools or state when not to use this tool, though this context is implicitly clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zecloud/remote-mcp-linkedin'

If you have feedback or need assistance with the MCP directory API, please join our Discord server