Skip to main content
Glama

RemoteHunt

Get job details

get_job
Read-onlyIdempotent

Details of one RemoteHunt job: title, company, stated pay, where it can hire, level, must-have skills, a short excerpt of the posting and the link to apply. Takes a RemoteHunt job link (remotehunt.app/job/...).

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": "<job>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYesA RemoteHunt job link or its slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description's real addition is the list of returned fields, which matters because no output schema exists. It still says nothing about error behavior, missing jobs, or truncation of the 'short excerpt'.

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?

Two sentences with no filler: the return contents lead, and the accepted input format follows. Slightly compressed into one long field list, but every clause carries information.

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 one-parameter, read-only lookup with no output schema, the description supplies the return shape and the accepted input format, which is the essential information. Only failure modes and excerpt behavior are left unspecified.

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 coverage is 100% and the single parameter is already documented as 'A RemoteHunt job link or its slug.' The description adds a concrete format example (remotehunt.app/job/...) but otherwise restates the schema, so baseline 3 is appropriate.

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 ('Details of one RemoteHunt job') and enumerates the fields returned, so an agent knows exactly what it gets back. It does not explicitly contrast itself with search_remote_jobs or can_job_hire_me, leaving sibling differentiation to inference from the word 'one'.

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 only implied: an agent can infer it should call this when it already holds a job link or slug and wants full detail. There is no explicit statement of when to prefer search_remote_jobs or can_job_hire_me, and no note on what happens with an invalid or expired link.

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