Rowfeed Search & Market Data

rowfeed/google-jobs-api

rowfeed--google-jobs-api

Destructive

This tool calls the Actor "rowfeed/google-jobs-api" and retrieves its output results. Actor description: Google Jobs listings for any search and location: title, employer, location, salary, contract type, posted date, source and apply link. Filters for date posted and job type, monitor mode for new jobs only. Licensed data, no blocked runs.

Input Schema

Name	Required	Description	Default
`onlyNew`	No	Return only jobs not returned in earlier runs with the same search, location and filters. Schedule it daily for job alerts.
`queries`	No	What you would type into Google, e.g. 'data analyst' or 'warehouse jobs'. Up to 500. Example values: ["data analyst"]
`language`	No	Language of the listings (English name). Example values: "English"	English
`location`	No	City, region or country in Google's format: 'City,Region,Country' or just 'United States'. Example values: "New York,New York,United States"	New York,New York,United States
`waitSecs`	No	Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
`datePosted`	No	Only jobs posted within this period.
`employmentTypes`	No	Optional: only these job types.
`maxJobsPerQuery`	No	Up to 200, in steps of 10. Example values: 50

Output Schema

Name	Required	Description
`tip`	No	Advisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key
`runId`	Yes	Actor run ID
`stats`	No	Run statistics
`status`	Yes	Run status: READY \| RUNNING \| TIMING-OUT \| TIMED-OUT \| ABORTING \| ABORTED \| SUCCEEDED \| FAILED
`actorId`	Yes	Stable Apify Actor ID from the run record
`summary`	Yes	Past-tense summary of the run state
`exitCode`	No	Actor process exit code; populated for terminal states (especially FAILED)
`nextStep`	Yes	One primary follow-up action with identifiers interpolated
`storages`	Yes	Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
`actorName`	No	"username/actor-name"
`startedAt`	No	ISO timestamp when the run started
`finishedAt`	No	ISO timestamp when the run finished (terminal states only)
`statusMessage`	No	Pass-through from Apify run.statusMessage
`apifyConsoleUrl`	No	Personalized Apify Console link to the run; present only for Console sessions

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026

addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema

Added value: +{
+  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
+  "properties": {
+    "apply_url": {
+      "type": "string"
+    },
+    "checked_at": {
+      "type": "string"
+    },
+    "contract_type": {
+      "type": "string"
+    },
+    "employer": {
+      "type": "string"
+    },
+    "employer_logo": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "employer_url": {
+      "type": "null"
+    },
+    "from_snapshot": {
+      "type": "boolean"
+    },
+    "google_url": {
+      "type": "string"
+    },
+    "job_id": {
+      "type": "string"
+    },
+    "job_location": {
+      "type": "string"
+    },
+    "language": {
+      "type": "string"
+    },
+    "location": {
+      "type": "string"
+    },
+    "posted_ago": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "posted_at": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "query": {
+      "type": "string"
+    },
+    "rank": {
+      "type": "number"
+    },
+    "salary": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "source": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedNov 6, 2026
- addedInput schema / properties / language / prefill
```
Added value: +"English"
```
- addedInput schema / properties / location / prefill
```
Added value: +"New York,New York,United States"
```
- addedInput schema / properties / queries / prefill
```
Added value: +[
+  "data analyst"
+]
```

Changed2 schema fields changedNov 6, 2026

addedInput schema / description

Added value: +"Live lookups need a paid Apify plan (any plan). The pre-filled example works on the free plan."

removedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema

Removed value: -{
-  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
-  "properties": {
-    "apply_url": {
-      "type": "string"
-    },
-    "checked_at": {
-      "type": "string"
-    },
-    "contract_type": {
-      "type": "string"
-    },
-    "employer": {
-      "type": "string"
-    },
-    "employer_logo": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "employer_url": {
-      "type": "null"
-    },
-    "from_snapshot": {
-      "type": "boolean"
-    },
-    "google_url": {
-      "type": "string"
-    },
-    "job_id": {
-      "type": "string"
-    },
-    "job_location": {
-      "type": "string"
-    },
-    "language": {
-      "type": "string"
-    },
-    "location": {
-      "type": "string"
-    },
-    "posted_ago": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "posted_at": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "query": {
-      "type": "string"
-    },
-    "rank": {
-      "type": "number"
-    },
-    "salary": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "source": {
-      "type": "string"
-    },
-    "title": {
-      "type": "string"
-    }
-  },
-  "type": "object"
-}

Changed1 schema field changedNov 6, 2026

addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema

Added value: +{
+  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
+  "properties": {
+    "apply_url": {
+      "type": "string"
+    },
+    "checked_at": {
+      "type": "string"
+    },
+    "contract_type": {
+      "type": "string"
+    },
+    "employer": {
+      "type": "string"
+    },
+    "employer_logo": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "employer_url": {
+      "type": "null"
+    },
+    "from_snapshot": {
+      "type": "boolean"
+    },
+    "google_url": {
+      "type": "string"
+    },
+    "job_id": {
+      "type": "string"
+    },
+    "job_location": {
+      "type": "string"
+    },
+    "language": {
+      "type": "string"
+    },
+    "location": {
+      "type": "string"
+    },
+    "posted_ago": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "posted_at": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "query": {
+      "type": "string"
+    },
+    "rank": {
+      "type": "number"
+    },
+    "salary": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "source": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedNov 5, 2026

removedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema

Removed value: -{
-  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
-  "properties": {
-    "apply_url": {
-      "type": "string"
-    },
-    "checked_at": {
-      "type": "string"
-    },
-    "contract_type": {
-      "type": "string"
-    },
-    "employer": {
-      "type": "string"
-    },
-    "employer_logo": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "employer_url": {
-      "type": "null"
-    },
-    "from_snapshot": {
-      "type": "boolean"
-    },
-    "google_url": {
-      "type": "string"
-    },
-    "job_id": {
-      "type": "string"
-    },
-    "job_location": {
-      "type": "string"
-    },
-    "language": {
-      "type": "string"
-    },
-    "location": {
-      "type": "string"
-    },
-    "posted_ago": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "posted_at": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "query": {
-      "type": "string"
-    },
-    "rank": {
-      "type": "number"
-    },
-    "salary": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "source": {
-      "type": "string"
-    },
-    "title": {
-      "type": "string"
-    }
-  },
-  "type": "object"
-}

Changed1 schema field changedNov 5, 2026

addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema

Added value: +{
+  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
+  "properties": {
+    "apply_url": {
+      "type": "string"
+    },
+    "checked_at": {
+      "type": "string"
+    },
+    "contract_type": {
+      "type": "string"
+    },
+    "employer": {
+      "type": "string"
+    },
+    "employer_logo": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "employer_url": {
+      "type": "null"
+    },
+    "from_snapshot": {
+      "type": "boolean"
+    },
+    "google_url": {
+      "type": "string"
+    },
+    "job_id": {
+      "type": "string"
+    },
+    "job_location": {
+      "type": "string"
+    },
+    "language": {
+      "type": "string"
+    },
+    "location": {
+      "type": "string"
+    },
+    "posted_ago": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "posted_at": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "query": {
+      "type": "string"
+    },
+    "rank": {
+      "type": "number"
+    },
+    "salary": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "source": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedNov 4, 2026

removedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema

Removed value: -{
-  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
-  "properties": {
-    "apply_url": {
-      "type": "string"
-    },
-    "checked_at": {
-      "type": "string"
-    },
-    "contract_type": {
-      "type": "string"
-    },
-    "employer": {
-      "type": "string"
-    },
-    "employer_logo": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "employer_url": {
-      "type": "null"
-    },
-    "from_snapshot": {
-      "type": "boolean"
-    },
-    "google_url": {
-      "type": "string"
-    },
-    "job_id": {
-      "type": "string"
-    },
-    "job_location": {
-      "type": "string"
-    },
-    "language": {
-      "type": "string"
-    },
-    "location": {
-      "type": "string"
-    },
-    "posted_ago": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "posted_at": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "query": {
-      "type": "string"
-    },
-    "rank": {
-      "type": "number"
-    },
-    "salary": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "source": {
-      "type": "string"
-    },
-    "title": {
-      "type": "string"
-    }
-  },
-  "type": "object"
-}

AddedOct 21, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare openWorldHint=true and destructiveHint=true, so the safety profile of kicking off an external Actor run is communicated structurally. The description adds real context beyond that — 'Licensed data, no blocked runs' and monitor mode semantics — but omits the monetization constraint that the input schema mentions (live lookups need a paid Apify plan) and doesn't clarify that calling it starts a run and consumes credits.

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?

The lead-in 'This tool calls the Actor ... and retrieves its output results' is boilerplate that adds little, but the actor description that follows is dense and front-loaded with the useful capability and filter information. No sentence is redundant enough to be a real liability.

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?

With an output schema present, return values need not be described, and the description covers capability, filters, and data-quality/licensing notes. The main gap is operational: the paid-plan requirement (visible only buried in the input schema description) and the relationship to waitSecs/get-actor-run polling are not surfaced here.

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%, including waitSecs polling behavior and the onlyNew monitor explanation, so the schema already carries parameter meaning. The description only restates the filter/monitor capabilities at a high level and adds nothing about query limits, location format, or maxJobsPerQuery beyond what the schema documents. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('calls the Actor ... and retrieves its output results') and resource (Google Jobs listings), then enumerates the returned fields: title, employer, location, salary, contract type, posted date, source, apply link. An agent can tell this is a Google Jobs scraper rather than a hotels/maps/SERP tool, though it never explicitly contrasts with the closest sibling, rowfeed--career-site-jobs-scraper.

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?

It implies usage through feature mentions ('Filters for date posted and job type, monitor mode for new jobs only') and the schema's onlyNew note about scheduling for job alerts, but it gives no explicit when-to-use/when-not-to-use guidance and never names an alternative tool. The agent must infer the routing decision.

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

All Rowfeed Search & Market Data tools Inspect

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.

rowfeed/google-jobs-api

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources