Skip to main content
Glama

AceRound AI Interview Copilot

create_interview_target

Create an interview target (company + role, optionally a job description) and return its ID for starting an interview. Same as "New target" on the website. (Requires the user's sign-in with scope interviews:write.)

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": {
      "name": "<name>"
    },
    "name": "create_interview_target"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRole title
companyNameNoCompany name
descriptionNoJob description, used as context when answering

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world write. The description adds genuinely new behavioral context: the required OAuth scope (interviews:write) and the fact that the created ID is the input to starting an interview. It does not discuss failure modes or duplicate-name 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?

Two tight sentences: purpose and return value first, then the website analogy and the auth requirement in parentheses. No filler, and the most important information is front-loaded.

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?

For a simple three-parameter create tool with annotations and no output schema, the description covers purpose, return value, workflow linkage, and auth scope. Only minor gaps remain, such as what happens on duplicate targets or whether companyName is truly optional in practice.

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 all three parameters are already documented, including that description is used as answering context. The description only restates the field set at a high level, adding no syntax or constraint detail beyond the schema, so the baseline 3 applies.

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 ('Create an interview target') and enumerates the payload (company + role, optional job description), plus the return value (its ID). It is clearly distinguishable from siblings like list_interview_targets and start_interview.

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 phrase 'return its ID for starting an interview' and the 'Same as "New target" on the website' analogy give clear context for when to reach for this tool. It stops short of naming an explicit alternative or a when-not condition, so it is not a full 5.

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