Skip to main content
Glama

get_job_salary

Read-onlyIdempotent

Extract structured salary and compensation data from public LinkedIn job details using a numerical job ID.

Instructions

Extract structured salary and compensation data from public job details.

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": {
      "id": "<id>"
    },
    "name": "get_job_salary"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesLinkedIn numerical job ID (e.g. '4481120122')

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.8
    • addedInput schema / properties / id / description
      Added value: +"LinkedIn numerical job ID (e.g. '4481120122')"
  2. First observedv0.1.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety and repeatability profile is fully covered without the description. The only added context is 'public', hinting that data may be unavailable for non-public postings, but nothing is said about missing salary fields, rate limits, or data freshness.

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?

It is a single front-loaded sentence with no filler or redundancy. Its brevity is efficient, though it leaves no room for the routing information an agent would find useful.

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?

An output schema exists, so return-value shape does not need explaining, and the single required parameter is fully documented. What remains missing is the decision context — when this beats get_job_details or analyze_salary_offer and what happens when a posting carries no salary data — which matters given the many overlapping siblings.

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% and the single 'id' parameter is documented in the schema as a LinkedIn numerical job ID with an example. The description adds no format, range, or sourcing detail beyond that, so baseline 3 applies.

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 uses a specific verb and resource ('Extract structured salary and compensation data') and scopes it to 'public job details', so the agent knows this returns pay data for a job posting rather than the posting itself. It stops short of explicitly distinguishing itself from siblings like get_job_details or analyze_salary_offer, which also touch compensation.

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 when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The phrase 'from public job details' weakly implies a job ID prerequisite, but the agent must infer whether to call this versus get_job_details or analyze_salary_offer on its own.

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