Skip to main content
Glama

100Hires - AI ATS & Recruitment Software

by com.100hires

hires_get_candidate_resume

Read-only

Get the primary resume for a candidate. Returns uuid, absolute download url (use Bearer auth), relative_time, file metadata, type. Use include='text_content' to also get the parsed plain-text content in a text field without downloading the file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCandidate ID (integer) or alias (string).
includeNoComma-separated optional fields. Use 'text_content' to add a `text` field with parsed plain-text resume content.

TDQS

A4.2/5.0
Behavior4/5

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

The description discloses important behavioral details: returns specific fields, the download url requires Bearer auth, and the include parameter adds text content. This adds value beyond the annotations, which only indicate read-only and non-destructive behavior.

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 two sentences, front-loaded with the core purpose, and efficiently packs return details and optional usage. No unnecessary words.

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?

Given the simple parameters and no output schema, the description covers the return fields and optional behavior. It lacks mention of error cases (e.g., missing resume), but is sufficient for basic use.

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?

The description builds on the schema by explaining that the include parameter accepts 'text_content' to add a `text` field, and clarifies the effect. Schema coverage is 100%, but the description adds practical usage context.

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 clearly states it gets the primary resume for a candidate, and specifies the returned fields (uuid, download url, etc.). It distinguishes from sibling tools like hires_get_candidate or hires_list_candidate_files by focusing specifically on the resume.

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?

The description explains what the tool does but does not explicitly state when to use it versus alternatives like hires_get_candidate or hires_download_attachment. No exclusion criteria or direct comparisons are given.

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

All 100Hires - AI ATS & Recruitment Software toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation4/5

Most tools have clearly distinct purposes due to specific entity and action combinations. However, with 133 tools, there is some overlap (e.g., multiple ways to move applications) and similar-sounding operations (e.g., batch_remove_tags vs remove_candidate_tag) that could cause confusion. The detailed descriptions help but the sheer number increases ambiguity.

Naming Consistency5/5

All tools follow a consistent 'hires_verb_noun' pattern with snake_case. Verbs are descriptive (create, list, get, delete, update, batch) and nouns match the domain entities (candidate, application, job, etc.). No mixing of conventions like camelCase or inconsistent verb styles.

Tool Count2/5

133 tools is excessive for a typical server scope. While a full-featured ATS requires many operations, this count suggests insufficient aggregation. Tools for similar entities (e.g., multiple update/delete variants) could be consolidated. The high number overwhelms the tool surface and increases complexity.

Completeness4/5

The tool set covers core CRUD operations for major entities (candidates, applications, jobs, companies, users, messages, forms, etc.) plus batch operations, webhooks, and advanced features like AI scoring and nurture campaigns. Minor gaps exist (e.g., no direct reporting/analytics tools), but most workflows can be executed.

Resources