Skip to main content
Glama

TrueInterview

List my Co-pilot conversations

list_my_conversations
Read-onlyIdempotent

The candidate's own conversations with TrueInterview's Career Co-pilot on the site, most recently used first: each one's title (its first question), when it started and when it was last used. Use it to pick up the context the candidate already gave the site, then read one with get_my_conversation. query narrows by words in the whole title (the title shown may be cut). page.total counts every match across the pages.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_my_conversations"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page.
limitNo
queryNoWords in the title, e.g. "Stripe".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description layers on behavior they can't express: results are ordered most-recently-used first, the title is literally the conversation's first question, and the displayed title may be truncated. It also discloses that page.total counts every match across pages, which prevents an agent from mistaking it for a page-size count.

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?

Front-loaded with the returned fields, followed by a usage route, then two parameter notes — a logical order with no filler sentences. The opening clause 'the candidate's own conversations ... on the site' is slightly padded, but the parenthetical and caveats each carry real information.

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?

With no output schema, the description takes on the burden of describing the return shape and does so (title, start time, last-used time, page.total), plus ordering and truncation caveats. The only unaddressed element is the `limit` cap, which the schema states numerically and is inferable for a simple list call.

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 67%, and the description meaningfully upgrades `query` by clarifying it matches words in the whole title while the displayed title may be cut — a distinction the schema's 'Words in the title' does not make. `page.total` semantics are explained, but `limit` is left undocumented in both schema and description.

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 ('candidate's own conversations with TrueInterview's Career Co-pilot on the site'), adds scope ('own') and ordering ('most recently used first'), and enumerates the returned fields. The explicit 'then read one with get_my_conversation' separates it from the retrieval sibling without needing either schema opened.

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?

'Use it to pick up the context the candidate already gave the site, then read one with get_my_conversation' names both the situation that selects this tool and the alternative that follows it. The list-then-fetch workflow is stated rather than left to inference.

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