Skip to main content
Glama

GTM Daily

Get a job

get_job_details
Read-onlyIdempotent

Details of one open job by slug or id, with a description excerpt and a link to the original posting page.

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

Input Schema

NameRequiredDescriptionDefault
job_id_or_slugYes

Output Schema

NameRequiredDescriptionDefault
okNo
codeNo
dataNo
statusYes
messageNo
warningsNo
next_stepNo
next_cursorNo
action_grantNo
approval_urlNo
correlation_idYes
missing_fieldsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds meaningful behavior beyond that: only *open* jobs are retrievable, and the payload returns an excerpt rather than the full posting plus an outbound link to the original page.

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?

One front-loaded sentence naming the action, the identifier input, and the returned content. Nothing is padded or 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?

With an output schema present, the description needn't enumerate return fields, and it still gives the gist (excerpt + link). It is nearly complete; only the not-found / closed-job behavior is left unstated.

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 description coverage is 0%, so the description must carry the load — and it does clarify that the single parameter accepts either a slug or an id, which the schema's bare 'job_id_or_slug: string' does not spell out. The 200-character limit and format specifics remain undocumented.

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 (retrieve details) and resource (one job), scoped by slug or id, and distinguishes itself implicitly from the list-style sibling search_jobs. It stops short of naming that sibling explicitly, so the differentiation is inferable rather than stated.

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 — you'd call this after finding a job via search_jobs or when you already hold an id/slug — but the description never says when to prefer this over search_jobs or what to do if the job is closed. No exclusions or prerequisites 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.

Resources