Skip to main content
Glama

get_job_details

Read-only

Get detailed community metrics for a specific job listing (applicants by status, average days per status, Community Signal) using its UUID.

The metrics window defaults to the last 30 days. When the user requests a longer period — e.g. "last 6 months", "last year", "since January" — compute startDate and endDate from that phrase and pass them explicitly.

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

Input Schema

NameRequiredDescriptionDefault
jobIdYesThe unique identifier (UUID) for the job listing.
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.
endDateNoEnd of the metrics window in ISO 8601 format. Defaults to today if omitted.
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.
startDateNoStart of the metrics window in ISO 8601 format (YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS). Compute from natural-language ranges: 'last 6 months' → today minus 6 months, 'last year' → today minus 12 months. Defaults to 30 days ago if omitted.
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
dataYes

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"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "jobId"
      -]New value: +[
      +  "jobId",
      +  "context"
      +]
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / properties / data / additionalProperties
      Previous value: -trueNew value: +{}
  3. First observed

TDQS

A3.7/5.0
Behavior3/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, and an output schema exists so return format need not be described. The description's genuine addition is the implicit 30-day default metrics window and the conditional override, though the same default and date-computation examples are already spelled out in the startDate schema description, so the added value is modest.

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 paragraphs with the core purpose front-loaded and the window behavior second; every sentence carries information and nothing is padded or redundant within the description itself.

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 read-only metrics lookup with full annotation coverage, a complete input schema and an output schema, the description covers purpose, scope and the one behavior that materially changes results (the date window). The only shortfall is silence on the required analytics parameters and how conversation_id should be carried forward, which the schema does document.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and every parameter including the analytics fields (context, llm_model, conversation_id) is documented in the schema. The description restates the date-range guidance already present in the startDate parameter description and says nothing about the required context/llm_model analytics parameters or the conversation_id threading, so it adds essentially no meaning beyond the schema.

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 ("Get detailed community metrics for a specific job listing") and enumerates the returned metrics (applicants by status, average days per status, Community Signal) plus the identifier type (UUID). An agent can distinguish this reporting tool from sibling application/company lookup tools without opening the schema.

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?

Provides conditional guidance for the time window: metrics default to the last 30 days and the agent should compute startDate/endDate when the user asks for a longer period, with concrete phrase examples. However, it offers no guidance on when to choose this tool over nearby siblings such as get_job_application or get_company_details, and no prerequisites or exclusions are stated.

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.