Skip to main content
Glama

Get a job on Faith Friendly Jobs

get_job
Read-only

Returns one current Faith Friendly Jobs job by its id, with a sanitized description of up to 8,000 characters and a link to its 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": {
      "id": "<id>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id of a job from a search_jobs result. The number at the end of that id works on its own too, as an integer or a string.

Output Schema

NameRequiredDescriptionDefault
jobYes
brandYes
premium_similarNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • removedOutput schema / properties / job / properties / categories / items / $ref
      Removed value: -"#/properties/job/properties/title"
    • addedOutput schema / properties / job / properties / categories / items / maxLength
      Added value: +500
    • addedOutput schema / properties / job / properties / categories / items / type
      Added value: +"string"
    • removedOutput schema / properties / job / properties / company / $ref
      Removed value: -"#/properties/job/properties/title"
    • addedOutput schema / properties / job / properties / company / maxLength
      Added value: +500
    • addedOutput schema / properties / job / properties / company / type
      Added value: +"string"
    • changedOutput schema / properties / job / properties / employment_type / anyOf
      Previous value: -[
      -  {
      -    "$ref": "#/properties/job/properties/title"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maxLength": 500,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / job / properties / experience_level / anyOf
      Previous value: -[
      -  {
      -    "$ref": "#/properties/job/properties/title"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maxLength": 500,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / job / properties / location / anyOf
      Previous value: -[
      -  {
      -    "$ref": "#/properties/job/properties/title"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maxLength": 500,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / job / properties / salary / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "max": {
      -        "type": [
      -          "number",
      -          "null"
      -        ]
      -      },
      -      "min": {
      -        "type": [
      -          "number",
      -          "null"
      -        ]
      -      },
      -      "type": {
      -        "anyOf": [
      -          {
      -            "$ref": "#/properties/job/properties/title"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      }
      -    },
      -    "required": [
      -      "min",
      -      "max",
      -      "type"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "max": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "min": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "type": {
      +        "anyOf": [
      +          {
      +            "maxLength": 500,
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      }
      +    },
      +    "required": [
      +      "min",
      +      "max",
      +      "type"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / job / properties / skills / items / $ref
      Removed value: -"#/properties/job/properties/title"
    • addedOutput schema / properties / job / properties / skills / items / maxLength
      Added value: +500
    • addedOutput schema / properties / job / properties / skills / items / type
      Added value: +"string"
    • addedOutput schema / properties / premium_similar / properties / count / maximum
      Added value: +9007199254740991
  2. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"The id of a job from a search_jobs result. The number at the end of that id works on its own too, as an integer or a string."
  3. First observed

TDQS

A3.8/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 still adds real context beyond that: the description field is sanitized and capped at 8,000 characters, and a link to the job page is included, which tells the agent to expect truncation. It does not cover the not-found/error case, which keeps it from a 5.

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?

A single sentence with the retrieval scope front-loaded and zero filler; every clause (single job, sanitized description, 8,000-char cap, page link) 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?

With an output schema present and annotations covering safety, the description needs only to establish scope and notable payload traits, which it does. The main omission is behavior on a missing or invalid id, which matters slightly for a lookup-by-key tool.

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% and the schema already explains where the id comes from and that the trailing integer works alone. The description only restates 'by its id' and adds no syntax, format, or fallback detail beyond the schema, so baseline 3 is appropriate for a one-parameter tool.

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 uses a specific verb and resource — 'Returns one current Faith Friendly Jobs job by its id' — which makes the single-record lookup unambiguous next to a list-oriented sibling. It stops short of naming search_jobs or explicitly contrasting the two, so differentiation is inferred 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?

'By its id' implies the tool is for retrieval after an id is known, but the description never says when to prefer this over search_jobs or what to do when the id is unknown (that routing hint lives only in the schema text). Usage is implied, not guided.

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