Skip to main content
Glama

Read a job

readJobListing
Read-onlyIdempotent

One job in full, by the jobId from any row: searchCleraRoles, listMatches, searchJobs or listSavedJobs.

kind clera is a role at a startup Clera works with: role has the description, tech stack, experience band, visa line, interview stages and the company block, and likeMatch is the next step. kind board is a role from the wider market: listing has the description, requirements, benefits and the company block, and applyToJob applies for them.

isOpen false means the role stopped hiring or the posting closed. Say so plainly rather than sending someone to a dead posting. Once a role is a match with an opportunityId, readMatch adds their status and role questions. Never show jobId.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "jobId": "<jobId>"
    },
    "name": "readJobListing"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesThe jobId from a searchCleraRoles, listMatches, searchJobs or listSavedJobs row.

Output Schema

NameRequiredDescriptionDefault
kindYes
roleYes
jobIdYes
isOpenYes
salaryYes
listingYes
locationYes
positionYes
arrangementYes
companyNameYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that: the per-kind field sets returned, the meaning of isOpen=false, the instruction never to expose jobId, and a disclosure that inputs and results are privately recorded for usage tracking. It does not cover what happens on an invalid or stale jobId, which keeps it off a 5.

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?

Front-loaded with the core purpose, then organized into kind-specific behavior, edge-case handling, and a privacy note. Dense but each paragraph carries operational information; the closing privacy sentence is boilerplate that could be trimmed without loss.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 shape need not be explained, and the description nonetheless characterizes what each kind yields. Combined with next-step routing, dead-posting guidance, and a display rule for jobId, an agent has everything needed to call this correctly in a single turn.

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 coverage is 100% and the schema description already tells the agent that jobId comes from a searchCleraRoles, listMatches, searchJobs or listSavedJobs row. The description restates essentially the same provenance, so it adds little beyond the structured field; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening line states a specific verb and resource ('One job in full, by the jobId') and immediately scopes the input's provenance to rows from searchCleraRoles, listMatches, searchJobs or listSavedJobs. It further splits the resource into two concrete variants (kind 'clera' vs kind 'board') and names what each contains, so an agent knows exactly what it is retrieving.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Routing is explicit: after a 'clera' listing the next step is likeMatch, after a 'board' listing it is applyToJob, and once a match has an opportunityId readMatch adds status and role questions. It also gives a handling rule for the edge case (isOpen false means the role closed – say so plainly instead of sending someone to a dead posting).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources