Skip to main content
Glama
Career Portal MCP Server

Career Portal MCP Server

search_linkedin_jobs

Search public LinkedIn job listings with bounded pagination. Filter by location, remote mode, and posting date to find relevant openings.

Instructions

Search public LinkedIn job listings with bounded pagination.

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": {
      "query": "<query>"
    },
    "name": "search_linkedin_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
locationNo
pageTokenNo
remoteModeNo
postedWithinDaysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. It only notes 'bounded pagination' (already visible as limit maximum 25 in the schema) and says nothing about authentication needs, rate limiting, result ordering, or what a response looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of filler, which is good structure. However, brevity here reads as under-specification rather than efficiency given the six undocumented parameters and absence of annotations.

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

Completeness2/5

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

A six-parameter search tool with zero schema descriptions, no annotations, and no output schema needs the description to explain filtering behavior and pagination mechanics. The current text leaves an agent without enough to invoke it confidently, especially around pageToken usage and recency filtering.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across six parameters, and the description adds no meaning for query, location, remoteMode, postedWithinDays, or pageToken. 'Bounded pagination' gestures at limit/pageToken but supplies no semantics beyond what the schema's min/max constraints already encode.

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 names a specific verb and resource ('Search public LinkedIn job listings'), which clearly separates it from generic search_jobs and from search_naukri_jobs by source. It stops short of naming those siblings explicitly, so the differentiation is inferable rather than stated.

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?

There is no guidance on when to choose this tool over search_jobs or search_naukri_jobs, nor on prerequisites such as whether a browser session is required. The word 'public' hints at unauthenticated listings but the agent must guess that implication.

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