Skip to main content
Glama

Remotejobify

Get a remote job

get_job
Read-onlyIdempotent

One job on Remotejobify by its id or its remotejobify.app link: who can apply, the lines from the listing that prove it, pay, and the job description.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe job id from search_jobs, or its link on remotejobify.app.
countryNoWhere the person lives, to say whether they can apply. Optional.

Output Schema

NameRequiredDescriptionDefault
idYes
payNo
urlYes
proofYes
titleYes
postedNo
companyYes
locationNo
all_proofNo
descriptionNo
who_can_applyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: the tool returns eligibility ('who can apply') plus the specific listing lines that substantiate that verdict, along with pay and the job description.

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?

A single front-loaded sentence with a colon-delimited list of what comes back; nothing is wasted. The phrasing ('the lines from the listing that prove it') is slightly indirect but compact.

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 documenting return values and annotations covering safety, the description only needs to convey purpose and the eligibility/evidence angle, which it does. The main residual gap is the absence of routing guidance to search_jobs when no id is available.

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%, so both parameters are already documented in the schema, establishing a baseline of 3. The description reinforces that the id may be a raw id or a remotejobify.app link and hints that eligibility depends on the person's location, but adds no syntax or format detail beyond the schema.

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?

The description states a specific resource and scope: a single job on Remotejobify, retrieved by id or by its remotejobify.app link. The singular 'one job' implicitly contrasts with the search-oriented siblings, but no sibling is named explicitly, so differentiation is left partly to inference.

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 rather than stated: the agent can infer it should call this once it has an id from a search. There is no explicit when-to-use/when-not framing and no named alternative (e.g., search_jobs) for the case where the agent lacks an id.

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