Skip to main content
Glama

linkdapi-the-best-linkedin-professional-data-api

by com.jojapi
OverviewAdmin

Search

get_api_v1_jobs_search

search jobs Group: jobs. Billing per call: 1 Credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
geoIdNoLinkedIn's internal geographic identifier (optional) Examples: 103644278,102571732 Note: Usually auto-detected from location
startNo*The starting index for pagination (0-based)* Default: 0 (first page) Increment by: 25 per page (LinkedIn's default page size) Example: start=25 (second page), start=50 (third page)
salaryNosalary Minimum salary range you're targeting Available Options: any - Any salary (default) 40k - $40,000+ per year 60k - $60,000+ per year 80k - $80,000+ per year 100k - $100,000+ per year 120k - $120,000+ per year Example: salary=100k
keywordNoThe job title, skills, or keywords to search for Examples: software engineer,nodejs developer,data scientist,product manager
regionsNoSpecific region codes for targeted search (optional) Examples: 102571732,103743442
jobTypesNojobTypes (comma-separated) The type of employment you're looking for Available Options: full_time - Full-time positions part_time - Part-time positions contract - Contract-based work temporary - Temporary assignments internship - Internship opportunities volunteer - Volunteer positions Example: jobTypes=full_time,contract
locationNoThe city, state, or region where you want to find jobs Examples: San+Francisco, New+York+City, London, Remote Format: Use + for spaces: San+Francisco+Bay+Area
companyIdsNoSpecific company LinkedIn IDs to filter results (comma-separated) Examples: 2499210,1337,104085107 Format: comma-separated numbers
experienceNoThe required experience level for the job Available Options: internship - Student internships entry_level - 0-2 years experience (Junior roles) associate - 2-4 years experience mid_senior - 4-8 years experience (Mid-level to Senior) director - 8+ years experience (Director level and above) Example: experience=entry_level,mid_senior
timePostedNoHow recently the job was posted Available Options: any - Any time (default) 24h - Past 24 hours 1week - Past week 1month - Past month Example: timePosted=1week
workArrangementNoThe work location arrangement Available Options: onsite - Office-based work remote - Fully remote work hybrid - Combination of office and remote Example: workArrangement=remote,hybrid

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions billing cost ('1 Credits') but does not disclose whether the operation is read-only, any authentication requirements, rate limits, or side effects. The term 'search' suggests a safe read, but that is not explicitly stated.

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 to the point, containing only the essential action and a billing note. It avoids fluff, but it could be slightly richer without becoming verbose; still, it is appropriately concise.

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?

The schema fully documents parameters, and there is no output schema, so return values need not be detailed. However, the description does not mention any edge cases, response format, or high-level behavior beyond 'search jobs', leaving some contextual gaps for a complete understanding.

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 has 100% coverage with detailed descriptions for each of the 11 parameters, including examples, allowed values, and formatting. The tool description adds no additional parameter information, so the baseline score of 3 is appropriate.

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 'search jobs' which identifies the verb and resource, and it is distinct from sibling search tools (e.g., search_people, search_companies). However, it lacks any detail about the specific filtering capabilities or the intended use case beyond the literal name.

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. While the name 'search jobs' implies the domain, there is no explicit comparison to sibling tools or mention of scenarios where this tool is preferred.

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

All linkdapi-the-best-linkedin-professional-data-api toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources