Skip to main content
Glama

compare_jobs

Read-onlyIdempotent

Compare 2-5 public LinkedIn jobs side-by-side on requirements, skills, seniority, and viability to identify the best fit.

Instructions

Compare 2-5 public LinkedIn jobs on requirements, skills, seniority, and viability.

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": {
      "ids": "<ids>"
    },
    "name": "compare_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesList of 2 to 5 LinkedIn numerical job IDs to compare side-by-side

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.8
    • addedInput schema / properties / ids / description
      Added value: +"List of 2 to 5 LinkedIn numerical job IDs to compare side-by-side"
  2. First observedv0.1.2

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already cover read-only, open-world, idempotent, non-destructive behavior, while the description adds the public-jobs-only limitation and comparison dimensions. It does not explain permission needs, invalid or private ID handling, or rate limits, so the added behavioral context is moderate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence covers verb, scope, count, and comparison dimensions. There is no redundant wording, and the output schema carries return structure.

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 one-parameter comparison tool with full schema coverage, rich annotations, and an output schema, the definition supplies enough to call it correctly. It could be stronger by noting how IDs are sourced or what happens with non-public IDs, but those are minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the ids parameter already documents 2-5 numerical LinkedIn job IDs. The description adds the constraint that jobs must be public, a small but meaningful semantic addition beyond the schema.

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 (Compare) and resource (2-5 public LinkedIn jobs) plus comparison dimensions, so the agent can identify it as a multi-job comparison tool. It does not explicitly name which sibling to use instead, so it falls short of full sibling differentiation.

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 implies usage for side-by-side comparison of 2-5 public LinkedIn jobs but never states when to choose it over get_job_details, analyze_job_viability, match_jobs_to_resume, or search_jobs. No exclusions or prerequisites are given.

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