Skip to main content
Glama

Save a job listing

saveJob
Idempotent

Bookmark a job board listing so it's there later.

Saving is private. It does not tell the company anything and it does not apply; applyToJob does that when they're ready.

Pass position and companyName exactly as the search result gave them. They are checked against the record, so a mismatch is refused rather than saving the wrong role.

Saving the same listing twice is fine and changes nothing.

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>",
      "position": "<position>",
      "companyName": "<companyName>"
    },
    "name": "saveJob"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesThe jobId from a searchJobs result, or a readJobListing result with kind board.
positionYesThe position exactly as the result gave it.
companyNameYesThe company name exactly as the result gave it.

Output Schema

NameRequiredDescriptionDefault
jobIdYes
isLiveYes
savedAtYes
positionYes
companyNameYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses privacy behavior, that the company is not notified, that this is not an application, that mismatched position/companyName values are refused, and that duplicate saves are no-ops. These details add meaningful behavioral context while remaining consistent with idempotentHint, destructiveHint, and readOnlyHint.

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?

The description is front-loaded with the core action, then proceeds through privacy, non-application behavior, parameter validation, idempotency, and data recording. Each sentence contributes relevant information without repetition or filler.

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?

For a simple three-parameter save operation with annotations and an output schema, the description covers purpose, privacy, non-application behavior, validation, idempotency, and logging. An agent has enough context to invoke the tool correctly without needing return-value details, since an output schema exists.

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%, so the schema already documents all three parameters. The description adds value by explaining that position and companyName must exactly match the source result and that mismatches are refused rather than saved. It does not add further semantics for jobId beyond what the schema already provides.

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 description states a specific verb and resource: "Bookmark a job board listing so it's there later." It also explicitly distinguishes the tool from applyToJob by saying it does not apply. This gives an agent enough to identify the tool's role without opening the schema.

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?

The description explains when to use it (bookmark for later), when not to use it (it does not apply), and names the alternative for applying: applyToJob. It also clarifies that saving the same listing twice is acceptable, which covers a common edge case.

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