Skip to main content
Glama

CuratorSearch

by com.curatorsearch
OverviewDiscussionsAdmin

search_jobs

Read-onlyIdempotent

Search live museum, gallery and curatorial job listings, gathered daily from institutions' own career pages. Returns up to 20 roles, newest first, each with its curatorsearch.com page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many roles to return, 1 to 20. Defaults to 10.
queryNoFree text matched against title, institution and location, e.g. 'registrar London'. Omit to browse everything.
regionNoRestrict to one world region.
categoryNoRestrict to one field of work.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesHow many live roles match, which may exceed the number returned.
resultsYesThe matching roles, newest first.
attributionNoSource credit to quote when citing these results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "Leadership",
-  "Curatorial",
-  "Education & Public Programmes",
-  "Archives",
-  "Collections",
-  "Conservation",
-  "Intern & Fellowship",
-  "Production",
-  "Other"
-]New value: +[
+  "Leadership",
+  "Curatorial",
+  "Education & Public Programmes",
+  "Archives",
+  "Collections",
+  "Conservation",
+  "Intern & Fellowship",
+  "Open Call & Residency",
+  "Production",
+  "Other"
+]
  2. Changed5 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Restrict to one field of work."
    • addedInput schema / properties / limit / description
      Added value: +"How many roles to return, 1 to 20. Defaults to 10."
    • changedInput schema / properties / query / description
      Previous value: -"Free text matched against title, institution and location, e.g. 'registrar London'."New value: +"Free text matched against title, institution and location, e.g. 'registrar London'. Omit to browse everything."
    • addedInput schema / properties / region / description
      Added value: +"Restrict to one world region."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "attribution": {
+      "description": "Source credit to quote when citing these results.",
+      "type": "string"
+    },
+    "results": {
+      "description": "The matching roles, newest first.",
+      "items": {
+        "properties": {
+          "category": {
+            "description": "CuratorSearch field, one of the category values.",
+            "type": "string"
+          },
+          "deadline": {
+            "description": "Application deadline as an ISO date, or null if none is given.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "institution": {
+            "description": "Museum, gallery or organisation advertising the role.",
+            "type": "string"
+          },
+          "location": {
+            "description": "City and country as stated, or null if the posting gives none.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "posted": {
+            "description": "ISO date the role was first seen on the board.",
+            "type": "string"
+          },
+          "region": {
+            "description": "CuratorSearch world region.",
+            "type": "string"
+          },
+          "salary": {
+            "description": "Pay exactly as the posting states it, or null -- most postings state none.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "Job title as advertised.",
+            "type": "string"
+          },
+          "url": {
+            "description": "The role's permanent page on curatorsearch.com.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "institution",
+          "category",
+          "region",
+          "posted",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "How many live roles match, which may exceed the number returned.",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total",
+    "results"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

The description adds meaningful behavior beyond annotations: it states the freshness ('live', 'gathered daily'), the result cap ('up to 20 roles'), the ordering ('newest first'), and the output format ('each with its curatorsearch.com page'). These details are not in the annotations (readOnlyHint, openWorldHint, etc.) and help an agent anticipate result characteristics, though it does not cover edge cases like empty results.

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

Conciseness5/5

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

The description is exactly two sentences, with the primary verb and purpose front-loaded. The first sentence states what it searches and the data source; the second states key output behaviors. There is no redundancy or filler - every clause contributes to understanding the tool.

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 read-only search tool with all-optional parameters, an output schema, and annotations covering safety, the description is quite complete: it explains the data source, result cap, ordering, and output format. The only minor gaps are edge-case behavior (e.g., no matches) and explicit routing to siblings, but these are not critical given the sibling names and schema.

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% (all four parameters - limit, query, region, category - have descriptive text and enums). The description itself adds no parameter-specific meaning, so the baseline of 3 is appropriate per the rubric; the schema carries the full semantic weight for parameters.

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?

The description uses a specific verb ('Search') and a concrete resource ('live museum, gallery and curatorial job listings') with a clear data source ('gathered daily from institutions' own career pages'). It distinguishes itself from siblings like get_job (which likely fetches a single job) and institution_jobs (which likely filters by institution) by describing a broad aggregated search across multiple institutions and job types.

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

Usage Guidelines3/5

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

The description implies this tool is for searching/browsing job listings broadly, but it gives no explicit guidance about when to prefer it over alternatives. It does not mention siblings or state exclusionary conditions (e.g., 'use get_job for a specific role ID'), so an agent must infer usage from the general purpose.

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

All CuratorSearch 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