Skip to main content
Glama
dpkdhingra91

AI Interview Agents MCP Server

list_screening_roles

Read-only

Retrieve your CV-screening roles to find role IDs, avoid duplicate screenings, and track progress with counts of candidates, screened, top matches, and scheduled interviews.

Instructions

List the authenticated user's screenings (CV-screening roles).

    Use this to find an existing screening's roleId (so you don't create a
    duplicate), or to report progress. Each row carries:
    {roleId, name, position, location, workMode, candidateCount,
    screenedCount, topMatches (score >= 60), scheduledCount, createdAt}.

    screenedCount == candidateCount means scoring has finished for that
    screening (the role-level done-signal for run_screening). topMatches is
    the count worth scheduling.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already declare readOnlyHint=true, but description adds context about completion condition and meaning of fields beyond safety. No contradictions.

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?

Concise, front-loaded with purpose, followed by actionable details in a compact structure.

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?

Fully covers all aspects: what it does, what fields are returned, how to interpret them, and how it ties to run_screening. No gaps.

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?

No parameters exist; baseline 4 as description adds no confusion. Schema coverage 100% trivial.

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?

Clear verb 'list' with specific resource 'screenings (CV-screening roles)', distinguishes from siblings by mentioning roleId and avoiding duplicates.

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?

Explicitly states when to use (find roleId to avoid duplicate, report progress) and provides signal for completion: 'screenedCount == candidateCount means scoring has finished'.

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