Skip to main content
Glama
Sign In

linkedin

by com.jojapi
OverviewDiscussionsAdmin

Search job postings

get_jobs_search

Use the jobId from a result with /jobs/detail/{jobId}. Group: Jobs. Billing per call: 1 Credits.

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": {
      "keyword": "<keyword>"
    },
    "name": "get_jobs_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of results per page.
geoIdNoLocation code. Türkiye is `102105699`; worldwide is `92000000`.
startNoOffset of the first result. Pass the `cursor` value from the previous response to fetch the next page.
keywordYesSearch term for the job title or description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions billing cost and group, and indirectly that results contain jobId. It omits read-only nature, pagination mechanics beyond schema hints, response format, or any rate limiting. The minimal disclosure falls short of the burden placed on the description.

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 very short and front-loaded with the most actionable instruction. The metadata lines about group and billing are compact. Nothing is verbose, though the purpose clarity suffers from oversimplification.

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?

With no annotations, no output schema, and only three brief sentences, the description leaves out key context: what a typical response looks like, how pagination should be handled with cursor, how geoId affects results, and what keyword does. It partially compensates by pointing to the detail endpoint, but overall it is incomplete for a search tool with 4 parameters.

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?

The input schema's description coverage is high (all 4 parameters are described with examples and defaults), so the baseline is 3. The tool description adds no additional parameter-level meaning; it only mentions jobId usage after results are obtained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does not explicitly state the tool's purpose. It implies a search/list behavior by instructing to use the jobId from a result with the detail endpoint, but the primary verb and resource are left to the title and name. This is enough to understand the basic function but is not as direct as a clear statement like 'Searches job postings by keyword'.

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 only usage guidance is a follow-up instruction to pass jobId to the detail endpoint. It does not explain when to use this tool versus sibling search tools (e.g., get_company_search, get_people_search), nor does it mention any exclusions or prerequisites for calling this endpoint.

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

All linkedin toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources