Skip to main content
Glama

LinkedIn Job Search

linkedin_job_search

[Acquire · 5 credits] Search LinkedIn job postings. Useful for tracking hiring signals at target companies. Costs 5 credits per call.

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": {
      "keywords": "<keywords>"
    },
    "name": "linkedin_job_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortByNoSort order. 'date' is the useful one for hiring signal. Default: relevance.
refreshNoBypass the cache and re-run the search live (costs 5 credits). Default false: a previously-fetched result is returned free, with how long ago it was retrieved.
keywordsYesJob title keywords (e.g. 'staff engineer python')
locationNoLocation filter (e.g. 'San Francisco, CA')
companyIdNoRestrict to a LinkedIn company ID (numeric, e.g. '1441'). Not a name or slug — resolve one first with linkedin_company_info (1 credit) or linkedin_company_search, both of which return the company's id.
postedLimitNoOnly jobs posted within this window.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / companyId / description
      Previous value: -"Restrict to a LinkedIn company ID (numeric, e.g. '1441'). Not a name or slug — resolve one first with linkedin_company_search, which returns each company's id."New value: +"Restrict to a LinkedIn company ID (numeric, e.g. '1441'). Not a name or slug — resolve one first with linkedin_company_info (1 credit) or linkedin_company_search, both of which return the company's id."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations cover the safety profile (destructiveHint=false, openWorldHint=true), and the description adds a genuinely useful fact they do not carry: a fixed 5-credit cost per call, stated twice for emphasis. It does not describe caching behavior or result cardinality, but the schema's refresh parameter covers caching. No contradiction with annotations.

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?

Three short sentences, front-loaded with the credit cost and resource name so the agent sees the price before deciding to call. The cost is stated twice (bracketed prefix plus trailing sentence), which is mild redundancy but not harmful.

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?

For a single-required-parameter search with a fully documented six-parameter schema and no output schema, the definition supplies what is needed to select and invoke it, including cost. The main omission is any indication of result volume or pagination, though that is a minor gap for a search endpoint.

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%, with detailed enum and format guidance including how to resolve companyId, so the schema does the heavy lifting. The description adds no parameter meaning beyond what is already structured, which is the expected baseline 3.

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 concrete verb and resource: 'Search LinkedIn job postings', which is unambiguous against siblings like linkedin_people_search or linkedin_post_search. It also states the business purpose ('tracking hiring signals at target companies'). It stops short of explicitly contrasting itself with any named alternative, so it lands at a clear 4 rather than a 5.

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

Usage Guidelines3/5

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

It provides one positive use case ('tracking hiring signals at target companies') but gives no when-not guidance, no prerequisites, and no pointer to a sibling tool such as linkedin_company_search for resolving company identifiers. Parameter-level hints exist (sortBy 'date' for hiring signal, refresh bypassing cache), but they live in the schema, not the description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources