Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

meta_jobs_search

Search Meta's public careers site by team, technology, location, employment type, remote status, and sort order to retrieve matching open jobs. Omit filters to get all open roles.

Instructions

Meta Jobs search. Searches Meta's public careers site (metacareers.com) with the same team/technology/location/employment-type/keyword/remote/sort filters the live search page offers. All filters are optional and combine with AND semantics; an empty request returns Meta's entire open-requisition catalog in one response. q matches team, technology, location, or ref/req-code names -- it is NOT a free-text search over job titles or descriptions. teams enum (org teams + technologies, both use the same field): Advertising Technology, AR/VR, Artificial Intelligence, Business Development & Partnerships, Communications & Public Policy, Creative, Data & Analytics, Data Center, Design & User Experience, Enterprise Engineering, Global Operations, Infrastructure, Internship - Business, Internship - Engineering, Tech & Design, Internship - PhD, Legal, Finance, Facilities & Admin, People & Recruiting, Product Management, Research, Sales & Marketing, Security, Software Engineering, Technical Program Management, University Grad - Business, University Grad - Engineering, Tech & Design, University Grad - PhD & Postdoc, Facebook, Messenger, Instagram, WhatsApp, Meta Quest. roles enum: Full time employment, Internship, Short term employment. results_per_page enum: all, five, ten.

Input Schema

NameRequiredDescriptionDefault
qNoFacet-name keyword: matches team, technology, location, or ref/req-code -- not a title/description search
rolesNoRepeatable employment-type filter (OR); see roles enum above
teamsNoRepeatable team-or-technology filter (OR); see teams enum above
officesNoRepeatable location-id filter (OR) in Meta's own id format, e.g. menlo-park, london -- not a closed enum
sort_by_newNoSort newest-first instead of relevance
is_remote_onlyNoRestrict to remote-only postings
results_per_pageNoResponse size cap: all, five, ten

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.17.5
    • addedInput schema / properties / offices / items
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / results_per_page / enum
      Added value: +[
+  "all",
+  "five",
+  "ten"
+]
    • addedInput schema / properties / roles / items
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / teams / items
      Added value: +{
+  "type": "string"
+}
  2. Added

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 well: it discloses the empty-request full-catalog behavior, AND combination semantics, and the surprising `q` scope limitation. It omits return shape, pagination/limit behavior beyond the size cap, and any rate-limit notes.

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-loads the purpose and semantics first, then the enum reference data. The enum list is long but is genuinely needed since the schema lacks the values, so it earns its space; minor redundancy in restating filter concepts.

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?

For a 7-param, no-annotation, no-output-schema search tool, this is largely complete: usage, semantics, and enums are covered. It could still say what a returned posting contains, since no output schema exists to carry that.

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% (baseline 3), but the description adds real value by listing the full teams, roles, and results_per_page enum values that the schema does not enumerate, and by clarifying that `q` matches facets rather than titles/descriptions.

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 (searches Meta's public careers site, metacareers.com) and enumerates the exact filter dimensions it exposes. Combined with the sibling names meta_jobs_job/meta_jobs_list, an agent can tell this is the search endpoint versus the detail/list endpoints.

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?

Explains that all filters are optional with AND semantics and that an empty request returns the entire catalog, plus a clear warning that `q` is a facet-name matcher, not free text. It does not explicitly name alternatives (e.g. meta_jobs_job for details), so it stops short of full routing guidance.

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