Skip to main content
Glama

Add good-fit example

addGoodFitExample
DestructiveIdempotent

Record a candidate the company liked as a good-fit example for a job.

When a company expresses positive feedback about a candidate, add their LinkedIn to the job's good-fit list. These examples improve future candidate matching.

Input (provide at least one of linkedinUrl or talentId):

  • jobId: Which job this good-fit example is for (resolve with the job tool's list command)

  • linkedinUrl: Direct LinkedIn URL. If the source text wraps it in link markup (e.g. <https://linkedin.com/in/name|Display Name>), extract just the URL

  • talentId: UUID of the talent, their LinkedIn URL will be resolved automatically

If the URL is already in the list, returns success with a note instead of erroring. Returns a refusal if the jobId doesn't belong to this company.

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

Input Schema

NameRequiredDescriptionDefault
jobIdYesThe UUID of the job this good-fit example applies to.
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
talentIdNoThe talentId of the candidate who is a good fit. Their LinkedIn URL will be resolved automatically. Provide this OR linkedinUrl.
linkedinUrlNoThe LinkedIn URL of the good-fit candidate. Provide this OR talentId.

Output Schema

NameRequiredDescriptionDefault
linkedinUrlYes
alreadyExistedYes
totalGoodFitExamplesYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

With annotations already declaring mutation and idempotency, the description adds real operational context: duplicate URLs return success with a note instead of erroring, and a refusal is returned when jobId belongs to another company. It also discloses the privacy/recording notice. The only gap is any statement about what the added record affects or whether it can be removed.

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 trigger and purpose, then a scannable bullet list for inputs and a short edge-case paragraph. The trailing privacy/recording sentence is boilerplate rather than tool-specific guidance, the one piece of text that does not fully earn its place.

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 single-record mutation with a full output schema, the definition covers trigger, input resolution, duplicate handling, and authorization refusals. Nothing an agent needs in order to call it correctly is missing, and return values are correctly left to the output schema.

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%, so the baseline is 3. The description genuinely adds meaning beyond the schema, though: it states at least one of linkedinUrl or talentId is required, explains talentId auto-resolves a LinkedIn URL, and instructs extracting a bare URL from link markup like <https://linkedin.com/in/name|Display Name>.

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 and resource: "Record a candidate the company liked as a good-fit example for a job," and reinforces it with the downstream effect ("These examples improve future candidate matching"). An agent knows exactly what is created, though the description never contrasts this with adjacent write tools such as addProspectNote or addAutopilotSearch.

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

Usage Guidelines4/5

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

Gives a concrete trigger condition: "When a company expresses positive feedback about a candidate," which is a real when-to-use signal rather than a restatement. It also points to the job tool's list command for resolving jobId. It stops short of naming when NOT to use it or which sibling handles adjacent note-taking.

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