Skip to main content
Glama

get_recommended_jobs

Retrieve personalized job recommendations from LinkedIn based on your profile and preferences to identify relevant career opportunities.

Instructions

Get your personalized recommended jobs from LinkedIn

Returns: List[Dict[str, Any]]: List of recommended jobs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The core handler function for the 'get_recommended_jobs' tool. It uses LinkedIn's JobSearch class configured to scrape recommended jobs and returns a list of job dictionaries. Includes error handling.
    @mcp.tool()
    async def get_recommended_jobs() -> List[Dict[str, Any]]:
        """
        Get your personalized recommended jobs from LinkedIn
    
        Returns:
            List[Dict[str, Any]]: List of recommended jobs
        """
        try:
            driver = safe_get_driver()
    
            logger.info("Getting recommended jobs")
            job_search = JobSearch(
                driver=driver,
                close_on_complete=False,
                scrape=True,  # Enable scraping to get recommended jobs
                scrape_recommended_jobs=True,
            )
    
            if hasattr(job_search, "recommended_jobs") and job_search.recommended_jobs:
                return [job.to_dict() for job in job_search.recommended_jobs]
            else:
                return []
        except Exception as e:
            return handle_tool_error_list(e, "get_recommended_jobs")
  • Registration point where register_job_tools(mcp) is called, which in turn registers the get_recommended_jobs tool via @mcp.tool() decorator.
    # Register all tools
    register_person_tools(mcp)
    register_company_tools(mcp)
    register_job_tools(mcp)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool returns a list of recommended jobs but lacks details on authentication needs, rate limits, personalization criteria, or potential side effects. This is inadequate for a tool that likely requires user context and API constraints.

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 concise and front-loaded, with the core purpose in the first sentence and return format in the second. However, the second sentence 'Returns: List[Dict[str, Any]]: List of recommended jobs' is somewhat redundant given the output schema, slightly reducing efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has an output schema (which covers return values) and no parameters, the description is minimally complete. However, it lacks context on personalization mechanics and doesn't compensate for the absence of annotations, making it adequate but with clear gaps for a tool that likely depends on user-specific data.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a baseline score of 4 for not adding unnecessary information beyond what the schema already provides.

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 clearly states the tool's purpose: 'Get your personalized recommended jobs from LinkedIn' specifies the verb (get), resource (recommended jobs), and source (LinkedIn). However, it doesn't differentiate from sibling tools like 'search_jobs' or 'get_job_details', which would require explicit comparison to achieve a score of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'search_jobs' or 'get_job_details'. It mentions 'personalized recommended jobs' but doesn't clarify the context (e.g., based on user profile, recent activity) or exclusions, leaving the agent without explicit usage instructions.

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/Logos-Parthenos-AI/linkedin-mcp-server'

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