Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tes_job_detail

Retrieve detailed information for a specific Tes teaching job posting by its numeric ID, including employer, location, salary, contract terms, dates, and application contact.

Instructions

Get a Tes teaching job. Returns detail for one job posting by its numeric id (the id field returned by tes-job-search): employer, location, salary, contract terms/types, dates, and application contact/URL, plus a short excerpt of the listing description rather than the full long-form HTML copy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTes job id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the return shape plus a real limitation: the listing body is a 'short excerpt... rather than the full long-form HTML copy,' which sets an accurate expectation. It omits any statement about auth requirements or error behavior for an unknown id.

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?

One front-loaded sentence opens with the purpose, then adds the id provenance and the field list with no filler. The trailing field enumeration is dense but each item earns its place by telling the agent what comes back.

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 no output schema and no annotations, the description has to describe the return payload, and it does so field-by-field while flagging the excerpt-vs-HTML caveat. Missing only edge-case behavior (invalid id, expired posting), which is minor for a single-param read tool.

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 coverage is 100% and the single param is documented as 'Tes job id', so baseline would be 3. The description goes slightly beyond by specifying the id is numeric and originates from tes_job_search results, which adds real disambiguation value.

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+resource ('Get a Tes teaching job... detail for one job posting by its numeric id') and enumerates the returned fields, which cleanly separates it from tes_job_search and tes_job_employer. An agent can identify this as the single-posting detail tool 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly ties invocation to the search flow by naming the id source ('the id field returned by tes-job-search'), which is genuine routing guidance. It does not, however, say when to prefer this over tes_job_employer or what to do if the id is stale/invalid, so the when-not side is missing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools