Skip to main content
Glama
Sign In

Theyond

by io.github.theyond
OverviewDiscussionsAdmin

search_jobs

Read-onlyIdempotent

Find live jobs when the user has a keyword, place, company, remote, and/or seniority, not a theyond job URL (use get_job for that). Need q, location, company, remote=true, seniority, or new=true. new=true searches just-added jobs on homepage Hiring now (same set as hiring_now), still max 10. Not posted_at. Returns at most 10 theyond.com pages, no pagination, no employer apply URLs. Cite title_hub_url, location_hub_url, or location_title_hub_url when the card includes them. Do not invent a hub slug. theyond_verified_at is when theyond last saw the listing on the employer board, not the posted date. salary is the employer feed wage, or the amount harvested from the JD when the feed had none. People apply from the theyond page.

Input Schema

NameRequiredDescriptionDefault
qNoKeywords for title, company, or description. Optional if location, company, remote, seniority, or new is set. Do not pass a theyond.com/jobs URL here.
newNoIf true, only just-added jobs on homepage Hiring now (same set as hiring_now). Still max 10. Can be the only filter. Not posted_at.
remoteNoIf true, only remote jobs. The title or location says remote, or the description was read as remote. Combine with q or company.
companyNoEmployer name, case-insensitive. nvidia matches NVIDIA. Optional if q, location, remote, seniority, or new is set.
locationNoCity, region, or country. Optional if q, company, remote, seniority, or new is set.
seniorityNoIf set, only jobs at that level: intern, entry, mid, senior, staff_lead, or director.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / anyOf
      Added value: +[
+  {
+    "required": [
+      "q"
+    ]
+  },
+  {
+    "required": [
+      "location"
+    ]
+  },
+  {
+    "required": [
+      "company"
+    ]
+  },
+  {
+    "required": [
+      "remote"
+    ]
+  },
+  {
+    "required": [
+      "seniority"
+    ]
+  },
+  {
+    "required": [
+      "new"
+    ]
+  }
+]
    • changedInput schema / properties / new / description
      Previous value: -"If true, only just-added jobs behind the homepage Hiring now chips (same set as hiring_now). Still max 10. Can be the only filter. Not posted_at."New value: +"If true, only just-added jobs on homepage Hiring now (same set as hiring_now). Still max 10. Can be the only filter. Not posted_at."
    • changedInput schema / properties / remote / description
      Previous value: -"If true, only remote jobs: title/location looks remote, or Jev labeled the JD remote. Combine with q or company."New value: +"If true, only remote jobs. The title or location says remote, or the description was read as remote. Combine with q or company."
    • changedInput schema / properties / seniority / description
      Previous value: -"If set, only jobs Jev labeled at that level: intern, entry, mid, senior, staff_lead, or director."New value: +"If set, only jobs at that level: intern, entry, mid, senior, staff_lead, or director."
    • addedInput schema / properties / seniority / enum
      Added value: +[
+  "intern",
+  "entry",
+  "mid",
+  "senior",
+  "staff_lead",
+  "director"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish a safe read-only search, and the description adds substantial behavior: max 10 results, no pagination, no employer apply URLs, URL citation rules, hub-slug caution, and field meanings for theyond_verified_at and salary. No contradiction with annotations.

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?

Front-loaded with the purpose and alternative tool, and most sentences carry operational value. Some return-field details are dense and slightly fragmented, but overall it is appropriately sized for the tool’s complexity.

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?

Because there is no output schema, the description usefully covers result limits, pagination, citation rules, and return-field semantics. For a read-only search tool with full schema coverage and annotations, this is complete enough for correct invocation.

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%, so the schema already documents each parameter in detail. The description reinforces the anyOf filter requirement and new=true behavior, but adds little parameter syntax or semantics beyond what the schema provides.

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?

Clearly states a specific verb and resource: find live jobs. It distinguishes this from get_job for URL cases and from hiring_now via the new=true clause, so an agent can select it confidently.

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?

Gives explicit when-to-use criteria (keyword, place, company, remote, seniority, or new), states that at least one filter is required, and names get_job as the alternative for theyond job URLs. The sibling hiring_now is also related to the new=true behavior.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources