Skip to main content
Glama

Read rejection reasons

readRejectionReasons
Read-onlyIdempotent

Read why the company rejected candidates for a role. list: jobId: show a job's recorded rejection reasons with their ids. Get jobId from readJob list.

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": {
      "command": "<command>"
    },
    "name": "readRejectionReasons"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdNolist/add/delete (required): the job UUID. Use the job tool's list command to find IDs.
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
commandYesWhich operation to run: list. The tool description explains each.

Output Schema

NameRequiredDescriptionDefault
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing that inputs and results are privately recorded for usage tracking and support — a behavioral fact an agent cannot infer from annotations and one that matters for sensitive hiring data.

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

Conciseness3/5

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

The purpose statement is front-loaded and the privacy note is compact, but the middle line 'list: jobId: show a job's recorded rejection reasons with their ids' is awkwardly stacked and duplicates the schema's own guidance. It is short overall but could be tightened into cleaner sentences.

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?

With an output schema present and full parameter coverage, the description does not need to explain return values, and it correctly covers purpose, the one command, ID sourcing, and a data-handling caveat. The only mild gap is the absence of explicit framing against the edit counterpart.

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 all three parameters are already documented, including the same pointer to the job tool's list command. The description's 'jobId: show a job's recorded rejection reasons' restates what the schema and annotations already convey, adding little new meaning.

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 opens with a specific verb and resource ('Read why the company rejected candidates for a role') and then names the single operation ('list'), so an agent knows exactly what is returned. It does not explicitly contrast itself with the sibling editRejectionReasons, so differentiation is implied by the verb rather than stated.

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 gives one concrete prerequisite — obtain the jobId from 'readJob list' — which is genuinely useful routing guidance. However, it never states when to use this versus editRejectionReasons or readApplication, and with only a 'list' command there is no further selection logic to explain.

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