Skip to main content
Glama

find_board

Read-onlyIdempotent

Locate a company's job board by name or job/careers link, check sample titles to avoid company mismatches, and return entries for your watchlist.

Instructions

Find a company's job board by name or by a job/careers link. Returns entries for the watchlist. A guessed board name can belong to another company: check the sample titles before adding one. Google (with YouTube and DeepMind) is one board, google:google (its US roles; google:google/any for all). So is Amazon (with AWS), amazon:amazon (its US roles; amazon:amazon/any for all). A Workday, Oracle Recruiting Cloud or Jibe board that isn't found by name is found from a link to a job on it. An Avature careers portal is host/portal (avature:careers.initech.example/careers); a name finds one only at name.avature.net/careers, so give a job link from any other. An iCIMS careers site is icims: (careers-.icims.com), or the whole host for another (icims:jobs-acme.icims.com); a name finds one at careers-.icims.com. A Jobvite careers site is jobvite: (jobs.jobvite.com/); a name finds one there. A Gem job board is gem: (jobs.gem.com/); a name finds one there. A Recruitee careers site is recruitee: (.recruitee.com); a name finds one there. A name that fits no board is looked up on the company's own site (.com, .ai, .io at /careers or /jobs), whose careers page links its board. A Comeet careers page is comeet:/ (comeet.com/jobs/initech/12.345); a link to it or a job on it finds it, a name doesn't (the uid is only in the link). A careers site that lists its job pages in a sitemap (their pages carrying schema.org JobPosting markup) is sitemap:, like sitemap:careers.example.com; a link to its careers page or a job on it finds it, a name doesn't. Hacker News' "Who is hiring?" thread is one board, hn:whoishiring (hn:whoishiring/N: the last N months'), found by "Hacker News" or the news.ycombinator.com/submitted?id=whoishiring link. A VC fund's portfolio job board (Consider, Getro, or the fund's own page) isn't found here: pass add_board vc:, like vc:jobs.example.vc (vc:host/path when the list isn't at /jobs). Use it before add_board; to track one job from its link, use add_application instead.

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": {
      "company": "<company>"
    },
    "name": "find_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesA company name ("Stripe"), or a link to one of its job postings or its careers page.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.3
    • addedInput schema / properties / company / description
      Added value: +"A company name (\"Stripe\"), or a link to one of its job postings or its careers page."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, openWorld, non-destructive), and the description adds real behavioral context: the lookup falls through from name to provider-specific patterns to the company's own domain, and some providers can only be resolved from a link. It also warns of a failure mode ("A guessed board name can belong to another company: check the sample titles"). Missing only what happens when nothing is found.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded correctly with purpose and scope in the first two sentences, but the body becomes a dense provider-by-provider enumeration that is hard to scan and mixes find_board input rules with add_board key syntax. The content is largely justified, yet the delivery is heavier than needed for a one-parameter lookup.

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?

An output schema exists, so return values need no explanation, and the description covers the tricky resolution cases and routing to add_board/add_application. Complete enough for an agent to call it correctly, though the boundary between where find_board stops and add_board's vc:<host> syntax begins could be cleaner.

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?

The schema documents the single `company` parameter at 100% coverage, but the description goes well beyond it by detailing which input forms resolve (host/portal for Avature, icims:<company> vs full host, jobvite:<company>, comeet:<company>/<uid>, sitemap:<host>, hn:whoishiring). It notably states which providers a bare name cannot resolve, which the schema does not convey.

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 and resource ("Find a company's job board by name or by a job/careers link") plus the return scope ("Returns entries for the watchlist"). It explicitly distinguishes itself from add_board and add_application, so an agent can route without opening sibling schemas.

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 an explicit ordering rule ("Use it before add_board") and a counter-case with the right alternative ("to track one job from its link, use add_application instead"). It also spells out when a name is sufficient versus when a job/careers link is required, per provider (Avature, Comeet, sitemap, VC boards), which is genuine when-to-use guidance.

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