Skip to main content
Glama
Career Portal MCP Server

Career Portal MCP Server

search_jobs

Find public LinkedIn or Naukri job listings by query, location, remote mode, and posting date, with bounded pagination to page through results.

Instructions

Search public LinkedIn or Naukri 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": {
      "provider": "<provider>",
      "query": "<query>"
    },
    "name": "search_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
locationNo
providerYes
pageTokenNo
remoteModeNo
postedWithinDaysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses only that listings are public and pagination is bounded; it says nothing about authentication/browser-session requirements, rate limits, whether results are scraped live or cached, or whether pagination tokens expire — all relevant given the surrounding auth and mutation tools.

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?

A single front-loaded sentence with zero filler and no redundant restatement of the name. It is efficient, though the terseness is as much under-specification as conciseness for a 7-parameter tool.

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?

For a 7-parameter search tool with no annotations, no output schema, and no parameter documentation, the description is far too thin. It should at minimum explain result shape, pagination flow, and prerequisites; none of that is present.

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 7 parameters, so the description must compensate and largely fails to. It only weakly signals the provider choice and a pagination bound; query, location, remoteMode, postedWithinDays, and pageToken semantics (format, expiry, how to obtain the next token) are entirely undocumented.

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 gives a specific verb ('Search') and resource ('public LinkedIn or Naukri job listings'), and 'bounded pagination' hints at the limit/pageToken mechanism. It does not distinguish itself from the sibling tools search_linkedin_jobs and search_naukri_jobs, which appear to cover the same ground per provider, so an agent still has to guess the routing.

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 use this multi-provider search versus the provider-specific search_linkedin_jobs / search_naukri_jobs siblings, and no mention of prerequisites such as the browser-login tools that appear alongside it. The only implied usage is 'search across two providers,' which the agent must infer.

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