Skip to main content
Glama

export_jobs

Idempotent

Export public LinkedIn job details by job ID to a local CSV, JSON, or Excel file for offline review and analysis.

Instructions

Export public job details to a local CSV, JSON, or Excel file.

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": "export_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
fmtNoExport file format: 'csv', 'json', or 'xlsx'csv
idsYesList of LinkedIn job IDs to export
filenameNoCustom output file name (optional)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.8
    • addedInput schema / properties / filename
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Custom output file name (optional)"
      +}
    • addedInput schema / properties / fmt / description
      Added value: +"Export file format: 'csv', 'json', or 'xlsx'"
    • addedInput schema / properties / ids / description
      Added value: +"List of LinkedIn job IDs to export"
  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?

The word 'local' usefully explains why readOnlyHint is false despite this being an export: a file is written to disk. 'Public' also signals a scope limit on the exported data. Beyond that the description adds nothing the annotations do not already cover — it is silent on whether existing files are overwritten, where files are written, and how confirmation interplays with destructiveHint=false and idempotentHint=true.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the extreme brevity leaves no room for the flow and side-effect information an export tool warrants.

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 values need not be described, and the annotations cover the safety profile. However, for a tool that writes files and appears paired with 'confirm_export', the description should disclose the invocation sequence and file-handling consequences; those omissions are material rather than cosmetic.

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%, so 'fmt' and 'ids' are already fully documented, including the enum values. The description restates the format options but says nothing about 'filename' (defaults, overwrite behavior) or about the nature of the job IDs, so it adds no meaning beyond the schema. 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?

States a specific verb ('export') and resource ('public job details') plus the destination media (local CSV/JSON/Excel), which separates it from search and analysis siblings. It does not name or distinguish itself from the closely related 'confirm_export' sibling, so an agent cannot tell from the description alone how the two relate.

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?

No when-to-use or when-not-to-use guidance is given, and no prerequisites are mentioned. The presence of a sibling named 'confirm_export' strongly suggests a two-step export flow, but the description never says whether this tool should be called first, whether confirmation is required, or what happens on repeat calls.

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