Skip to main content
Glama

Theyond

by com.theyond
OverviewDiscussionsAdmin

search_jobs

Read-onlyIdempotent

Find live jobs when the user has a keyword, place, company, and/or remote, not a theyond job URL (use get_job for that). Need q, location, company, or remote=true. Returns at most 10 theyond.com pages, no pagination, no employer apply URLs. theyond_verified_at is when theyond last saw the listing on the employer board, not the posted date. People apply from the theyond page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoKeywords for title, company, or description. Optional if location, company, or remote is set. Do not pass a theyond.com/jobs URL here.
remoteNoIf true, only jobs whose title or location looks remote. Combine with q or company.
companyNoEmployer name, case-insensitive. nvidia matches NVIDIA. Optional if q, location, or remote is set.
locationNoCity, region, or country. Optional if q, company, or remote is set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / company / description
      Previous value: -"Employer name, case-insensitive. Shopify matches Shopify and Shopify Inc. Optional if q, location, or remote is set."New value: +"Employer name, case-insensitive. nvidia matches NVIDIA. Optional if q, location, or remote is set."
  2. Changed4 schema fields changed
    • addedInput schema / properties / company
      Added value: +{
+  "description": "Employer name, case-insensitive. Shopify matches Shopify and Shopify Inc. Optional if q, location, or remote is set.",
+  "type": "string"
+}
    • changedInput schema / properties / location / description
      Previous value: -"City, region, or country. Optional if q is set. Combine with q to narrow."New value: +"City, region, or country. Optional if q, company, or remote is set."
    • changedInput schema / properties / q / description
      Previous value: -"Keywords for title, company, or description. Optional if location is set. Do not pass a theyond.com/jobs URL here."New value: +"Keywords for title, company, or description. Optional if location, company, or remote is set. Do not pass a theyond.com/jobs URL here."
    • addedInput schema / properties / remote
      Added value: +{
+  "description": "If true, only jobs whose title or location looks remote. Combine with q or company.",
+  "type": "boolean"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"City, region, or country"New value: +"City, region, or country. Optional if q is set. Combine with q to narrow."
    • changedInput schema / properties / q / description
      Previous value: -"Keywords (title, company, description)"New value: +"Keywords for title, company, or description. Optional if location is set. Do not pass a theyond.com/jobs URL here."
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, openWorld, idempotent, non-destructive), and the description adds substantive behavior beyond them: a 10-page result cap, no pagination, no employer apply URLs, the meaning of theyond_verified_at versus posted date, and where users apply from.

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?

Dense and front-loaded with the routing rule first, and nearly every clause carries distinct information. The trailing sentence about applying from the theyond page is useful but slightly tangential to invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so: result cap, absence of pagination, absence of apply URLs, and the semantics of a notable field. Nothing essential for correct invocation is missing.

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 already 100%, so baseline is 3, but the description adds a cross-parameter constraint the schema does not encode: at least one of q/location/company/remote must be set. Field-level meanings themselves remain entirely in the schema.

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 (find live jobs) and explicitly carves out the sibling case: URLs go to get_job, not here. An agent can distinguish search_jobs from get_job without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit when-to-use ('when the user has a keyword, place, company, and/or remote'), explicit alternative ('use get_job' for a job URL), and the minimum input condition ('Need q, location, company, or remote=true'). No inference required.

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

All Theyond toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources