Skip to main content
Glama

fetch_person

Retrieve a LinkedIn user's basic profile information and optionally their experience, education, skills, posts, comments, reactions, and more.

Instructions

Allows you to open a person page to retrieve their basic information and perform additional person-related actions if needed. (st.openPersonPage action). Allows additional optional retrieval of experience, education, skills, languages, posts, comments and reactions. āš ļø PERFORMANCE WARNING: Only set additional retrieval flags to true if you specifically need that data. Each additional parameter significantly increases execution time: šŸ’” Recommendation: Start with basic info only. Only request additional data if the user explicitly asks for it or if it's essential for the current task.

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
personUrlYesThe LinkedIn profile URL of the person to fetch (e.g., 'https://www.linkedin.com/in/john-doe')
retrievePostsNoOptional. Whether to retrieve the person's posts information. Default is false.
retrieveSkillsNoOptional. Whether to retrieve the person's skills information. Default is false.
retrieveCommentsNoOptional. Whether to retrieve the person's comments information. Default is false.
retrieveEducationNoOptional. Whether to retrieve the person's education information. Default is false.
retrieveLanguagesNoOptional. Whether to retrieve the person's languages information. Default is false.
retrieveReactionsNoOptional. Whether to retrieve the person's reactions information. Default is false.
retrieveExperienceNoOptional. Whether to retrieve the person's experience information. Default is false.
postsRetrievalConfigNoOptional. Configuration for retrieving posts. Available only if retrievePosts is true.
commentsRetrievalConfigNoOptional. Configuration for retrieving comments. Available only if retrieveComments is true.
reactionsRetrievalConfigNoOptional. Configuration for retrieving reactions. Available only if retrieveReactions is true.
Behavior5/5

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

With no annotations, the description discloses the asynchronous workflow behavior, including immediate pending/running status, need to poll get_workflow_result, and prohibition on retrying while running. It also explains pendingReason variants (queued vs outsideWorkingHours), providing essential operational 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 structured with a clear purpose sentence, a performance warning, and a workflow explanation. While somewhat lengthy, each section earns its place and is logically organized, though it could be tightened slightly.

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 complexity (async workflow) and lack of an output schema, the description thoroughly explains the initial response shape, how to retrieve the final result via get_workflow_result, and both pending reasons. It covers all necessary operational aspects for correct invocation.

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 schema already covers all parameters at 100% coverage, so baseline is 3. The description adds value by warning that each additional retrieval flag increases execution time and recommending judicious flag usage, which informs how to set parameters beyond their type descriptions.

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 clearly states the tool opens a person page, retrieves basic info, and optionally retrieves experience, education, skills, languages, posts, comments, and reactions. It also names the underlying action (st.openPersonPage) and distinguishes from siblings like fetch_company/fetch_post/fetch_job by focusing on person-specific retrieval.

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?

It provides clear context for when to use the tool (when you have a person URL) and gives explicit guidance on when to set additional retrieval flags, warning that they significantly increase execution time. It also instructs to start with basic info and request more only if needed, though it doesn't explicitly name alternative tools or when-not-to-use.

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