Skip to main content
Glama

list_career_entries

Read-only

Returns the user's career journal entries from GigHQ, newest first. Supports optional filtering by entry type and date range.

Use this tool to:

  • Review what the user has already documented before starting a journaling session

  • Find entries to update or refine

  • Identify gaps (roles with few or no entries)

  • Synthesise entries into resume bullets or interview stories

Entry type filter values: 1=achievement, 2=project, 3=skill_acquired, 4=reflection.

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

Input Schema

NameRequiredDescriptionDefault
skipNoNumber of entries to skip for pagination.
takeNoNumber of entries to return (default 25, max 100).
typeNoFilter by entry type: 1=achievement, 2=project, 3=skill_acquired, 4=reflection. Omit for all types.
contextYesA few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other personal details.
end_dateNoISO 8601 end date to filter entries on or before, e.g. '2024-12-31'.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
start_dateNoISO 8601 start date to filter entries on or after, e.g. '2024-01-01'.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Output Schema

NameRequiredDescriptionDefault
totalYes
entriesYes
returnedYes
profileUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as \"a customer\". Do not quote the user or include names, emails, or other personal details.",
      +  "type": "string"
      +}
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The model identifier you are running as, for example \"claude-opus-4-8\" or \"gpt-5.2\". Pass \"unknown\" if you are not certain. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "context"
      +]
  2. Changed4 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / skip / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / returned / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / total / maximum
      Added value: +9007199254740991
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral facts beyond those annotations: results are ordered newest-first and two optional filters narrow the result set. It does not mention pagination behavior or result volume, which are left to the schema.

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 core action and ordering in the first sentence, then a scannable bulleted usage list. Minor waste: the entry-type value mapping is repeated verbatim from the schema, consuming a trailing line that earns little.

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?

With an output schema present, return values need not be described, and the definition covers read safety, ordering and filtering adequately for a read-only list tool with 8 well-documented parameters. The only gaps are pagination behavior and differentiation from sibling list tools, neither of which is critical to a correct call.

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 description coverage is 100%, so the schema already documents skip, take, type, start_date, end_date, context, llm_model and conversation_id. The description only restates the entry-type enum (1=achievement … 4=reflection), which is already in the schema verbatim, and adds no semantics for the date or pagination parameters. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource ('Returns the user's career journal entries from GigHQ') plus ordering ('newest first') and filter scope (entry type, date range). It does not explicitly differentiate itself from sibling list_experiences or explain how a journal entry differs from an experience record, so the agent must infer the distinction from naming alone.

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 'Use this tool to' block gives four concrete scenarios: reviewing before journaling, finding entries to update, spotting role gaps, and synthesising resume bullets. That is clear when-to-use guidance, but no when-NOT-to-use or named alternative (e.g. list_experiences, add_career_entry) is offered, so routing between siblings remains partially inferred.

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.