Skip to main content
Glama
Sign In
mcp-lightcast

mcp-lightcast

by lawwu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Bulk Retrieve Titles

bulk_retrieve_titles
Read-onlyIdempotent

Retrieve up to 1,000 Lightcast job titles in a single request by passing title IDs, reducing multiple API calls for bulk title lookups.

Instructions

Retrieve multiple titles in one request.

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": {
      "title_ids": "<title_ids>"
    },
    "name": "bulk_retrieve_titles"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNolatest
title_idsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety and idempotency are covered. The description adds only the batch nature of the call, and says nothing about partial failures when some ids are unknown, ordering of results, or how the version parameter affects resolution.

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 short sentence with the core purpose front-loaded and zero filler. It is efficient, though the brevity tips into under-specification rather than earned tightness.

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?

An output schema exists, so return values need not be described, but for a bulk read with an opaque version selector and a 1000-item cap the description omits anything an agent needs beyond the raw schema. It gives no indication of how missing or invalid titles are handled, which matters most for a batch tool.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters, so the description carries the full burden and does not meet it. It never explains that title_ids is a bounded array (1–1000) or what "version" with default "latest" actually selects.

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 pairs a specific verb ("Retrieve") with a specific resource ("titles") and adds the batch qualifier "multiple ... in one request," which distinguishes it from single-title lookups. It stops short of naming any sibling such as get_titles_metadata or search_job_titles, so the differentiation is implied rather than explicit.

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 guidance: nothing says to prefer this over search_job_titles when you already hold IDs, nor when to fall back to a single-title tool. The only cue is the word "multiple," from which an agent must infer the bulk-vs-single split.

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

Deploy Server

Other Tools