Skip to main content
Glama
jobinja-employer-mcp

jobinja-employer-mcp

by saeedsepehr

Get resume text

get_resume_text
Read-only

Extract plain text from an applicant's PDF resume and truncate it to a set character limit for token-efficient candidate review; use download_resume for image-only PDFs.

Instructions

Extracted plain text of an applicant's PDF resume, truncated to max_chars.

Much cheaper in tokens than reading the PDF itself. Scanned (image-only) PDFs give little or no text; use download_resume for those.

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": {
      "post": "<post>",
      "applicant_id": "<applicant_id>"
    },
    "name": "get_resume_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
postYes
max_charsNo
page_hintNo
applicant_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds genuinely useful context beyond that: output is truncated to max_chars, it is cheap in tokens relative to the PDF, and scanned PDFs degrade to little or no text. It doesn't say what happens at the truncation boundary or whether page_hint changes the extraction window.

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?

Three short sentences, front-loaded with what the tool returns, then the cost rationale, then the failure mode and escape hatch. Every sentence carries information an agent needs.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only extraction tool with no output schema, the description covers the return shape, truncation, and the scanned-PDF failure mode well. However, with 0% schema coverage across four parameters, the unexplained page_hint and the underspecified post/applicant_id identifiers leave the invocation contract incomplete.

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%, so the description must carry the parameter meaning, and it only explains max_chars (via the truncation clause). post and applicant_id are only indirectly gestured at, and page_hint is entirely undocumented in both the schema and the description, leaving a required identifier and an optional hint unexplained.

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?

States a specific verb and resource ('Extracted plain text of an applicant's PDF resume') plus the truncation behavior, so the agent knows exactly what it gets back. It also implicitly distinguishes itself from download_resume by naming that sibling as the alternative for scanned PDFs.

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?

Explicitly names the condition that selects the alternative: image-only PDFs should go to download_resume, and the token-cost note explains why this tool is preferred otherwise. It does not cover other contextual decisions, such as when to prefer get_applicant or how page_hint should influence the choice.

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