Skip to main content
Glama
dpkdhingra91

AI Interview Agents MCP Server

add_screening_candidates

Attach parsed CVs to a screening for scoring. Accepts CV data with or without email; returns counts of saved, skipped, and candidates without email for further action.

Instructions

Attach parsed CVs to a screening as candidates, ready to be scored.

    Pass the rows returned by parse_cvs straight through — each
    {"identity": {...}, "details": {...}} row is reshaped automatically into
    what the backend needs. Already-flat dicts ({firstName, lastName, email,
    summary, parsedResumeData, number, location}) also work.

    Email is NOT required here — screening scores a CV, it doesn't message
    anyone. CVs with no email are kept and given an unroutable placeholder so
    they still rank; the response's 'withoutEmail' count tells you how many.
    Those rows CANNOT be scheduled later until a real email is added — surface
    that number to the user.

    Returns {savedCount, skippedEmpty (CVs with no readable content),
    withoutEmail, candidates}. After this, call run_screening(role_id).
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
role_idYes
candidatesYes
Behavior5/5

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

Annotations indicate write operation (readOnlyHint=false) and not destructive. The description adds significant behavioral details: email is not required, CVs without email get a placeholder and are counted in withoutEmail, and they cannot be scheduled later until email is added. This goes beyond annotations.

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?

The description is multi-sentence but front-loaded with the main purpose. Every sentence adds value, though slightly verbose. Could be trimmed slightly but still concise.

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?

Despite no output schema, the description explains the return fields (savedCount, skippedEmpty, withoutEmail, candidates) and provides next-step guidance (call run_screening). This is complete for the tool's complexity.

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 0%, but the description compensates by explaining the candidates parameter accepts two formats (rows from parse_cvs or flat dicts) and details the structure. role_id is not explained, but the main complex parameter is well described.

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 the tool attaches parsed CVs to a screening as candidates. It specifies the input format (rows from parse_cvs or flat dicts) and distinguishes itself from sibling tools like schedule_screened_candidates by implying it's the step before run_screening.

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?

The description tells when to use (after parse_cvs) and provides clear context about email handling and the next step (call run_screening). It does not explicitly state when not to use or mention alternatives, but the usage is well-scoped.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dpkdhingra91/aiia-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server