Skip to main content
Glama

AceRound AI Interview Copilot

rename_interview

Rename an interview record (live or mock). (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": {
      "interviewId": "<interviewId>",
      "title": "<title>"
    },
    "name": "rename_interview"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
interviewIdYesInterview id from list_interviews

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is known. The description adds real value by naming the required auth scope (interviews:write), but says nothing about idempotency, failure modes, or whether the record's other fields are untouched.

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 short clauses, purpose front-loaded and the auth caveat parenthesized at the end. Every phrase carries information and nothing is repeated from the schema.

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 two-parameter, non-destructive rename with no output schema, purpose, scope, and authorization are all covered. Minor gaps remain around post-condition (what the returned or updated record looks like), which is low-stakes for this operation.

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?

With schema coverage at 50%, the schema documents interviewId's provenance ("from list_interviews") and title's length bounds. The description only implies that interviewId may reference either a live or mock interview; it adds nothing about title constraints, trimming, or uniqueness.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ("Rename an interview record") and adds scope ("live or mock"), letting an agent distinguish it from delete_interview or update_interview_preference. It stops short of explicitly naming a sibling it contrasts with, so it is clear but not maximally differentiated.

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?

Usage is implied by the verb plus the "live or mock" scope, and the auth prerequisite is stated. There is no explicit when-not-to-use guidance or routing to alternatives such as update_interview_preference for non-title edits.

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