Apify tools for products, Google ads, company signals, jobs, keywords, SEO and YouTube transcripts.
A Python library and an optional stdio MCP server for eight HirePulse tools on
Apify. Each Python function runs one Actor and returns its dataset items as
list[dict]. Tools run on the Apify Store, pay per use, with no subscription.
Apify already hosts MCP for these tools. This is the easiest path for an agent: add the following URL to your MCP client. No local Python installation is needed for this option.
Paste this hosted URL into your MCP client's remote-server configuration:
https://mcp.apify.com?tools=hirepulse/aliexpress-search-scraper,hirepulse/google-ads-transparency-scraper,hirepulse/company-intent-radar,hirepulse/google-jobs-scraper,hirepulse/ats-job-pulse,hirepulse/keyword-search-volume,hirepulse/domain-seo-overview,hirepulse/youtube-transcript-scraper
For one tool, use, for example, Google Ads hosted MCP. Use your client's Apify authentication setup. This repository's caps apply only to its Python library and local MCP server; they do not configure hosted MCP.
For Claude Desktop, Apify also provides this command:
npx -y @apify/actors-mcp-server --tools hirepulse/google-ads-transparency-scraper
Set APIFY_TOKEN in the server process environment through your launch setup.
Use the desired hirepulse/<tool> in --tools. Keep the token out of configuration
files and command arguments.
Python 3.10 or later is required. From this project directory:
python -m venv .venv
# Activate .venv using your shell, then:
python -m pip install .
For the self-hosted / customizable MCP server:
python -m pip install ".[mcp]"
python -m hirepulse_tools.mcp_server
The equivalent console command is hirepulse-mcp. It uses stdio.
Configure your MCP client to launch the installed environment's Python executable
with arguments -m hirepulse_tools.mcp_server, inheriting APIFY_TOKEN from its
process environment. Actor logs are not forwarded to stdio.
Provide APIFY_TOKEN in the environment before calling any tool. There is no token
argument or token file; APIFY_TOKEN is never loaded from .env. .env.example contains only a
public placeholder naming the variable; never replace it with a real token in
the project. Listing MCP tools requires no token and does not start an Actor.
These are executable input examples, not measured output examples. Running them
starts Apify Actors and can incur charges. Each script in examples/ uses a
5-row result limit and a USD 0.10 spending cap. Tests never run these scripts.
| Function | Tool page | Returns |
|---|---|---|
search_aliexpress | AliExpress Search Scraper | Product search records |
google_ads_by_domain | Google Ads Transparency Scraper | Ads, or one summary per domain |
company_intent | Company Intent Radar | One signal report per company |
google_jobs | Google Jobs Scraper | Job search records |
ats_jobs | ATS Job Scraper | Jobs and/or company summaries |
keyword_volume | Keyword Search Volume | Keyword metrics and ideas |
domain_seo | Domain SEO Overview | Domain overview, keyword and competitor records |
youtube_transcripts | YouTube Transcript Scraper | Transcript records, optionally with timestamps |
from hirepulse_tools import search_aliexpress
items = search_aliexpress(["wireless earbuds"], result_limit=5, max_total_charge_usd=0.10)
from hirepulse_tools import google_ads_by_domain
items = google_ads_by_domain(["nike.com"], mode="summary", result_limit=5, max_total_charge_usd=0.10)
from hirepulse_tools import company_intent
items = company_intent(["stripe.com"], result_limit=5, max_total_charge_usd=0.10)
from hirepulse_tools import google_jobs
items = google_jobs(["data engineer"], country="US", result_limit=5, max_total_charge_usd=0.10)
from hirepulse_tools import ats_jobs
items = ats_jobs(["stripe.com"], output_mode="summary_only", result_limit=5, max_total_charge_usd=0.10)
from hirepulse_tools import keyword_volume
items = keyword_volume(["running shoes"], result_limit=5, max_total_charge_usd=0.10)
from hirepulse_tools import domain_seo
items = domain_seo(["notion.so"], top_keywords=0, competitors=0, result_limit=5, max_total_charge_usd=0.10)
from hirepulse_tools import youtube_transcripts
items = youtube_transcripts(["https://www.youtube.com/watch?v=dQw4w9WgXcQ"], result_limit=5, max_total_charge_usd=0.10)
See all arguments, defaults and allowed values. Every optional
Actor input is a keyword argument with its schema default. Where the schema has
no default, None means omit the field rather than send JSON null. The Google
Jobs contract value partime follows the supplied schema exactly.
Every function also accepts these wrapper options, outside run_input:
| Option | Default | Behavior |
|---|---|---|
result_limit | 60 | Integer 1–1000; passed as .call(max_items=...) and .list_items(limit=...); at most this many rows are returned |
max_total_charge_usd | 1.0 | Finite positive USD amount, converted to Decimal for .call() |
The installed apify-client 3.3.0 signature was inspected to confirm both options.
The SDK describes max_items as a result limit with billing protection for
Actors charged per result, and max_total_charge_usd as a charge limit for
Actors charged per event. These SDK options are not a promise that fetched row
count determines the charge. Keep input batches small too. Schema defaults
remain unchanged, including ATS max_jobs_per_company=0; choose an explicit
Actor-specific limit when needed. See SDK verification.
Dataset rows are returned unchanged, in dataset order. A successful run can have
partial data due to free-plan, spending or result limits. Empty datasets return
[]. The library does not fetch key-value-store run summaries or promise a
complete dataset. Use the tool page and Apify run details when completeness
matters.
MissingTokenError explains how to provide the environment variable.
ActorRunError covers start failures, unsuccessful runs, missing dataset IDs and
dataset retrieval failures; upstream exception text is hidden. Invalid local
arguments raise ValueError before starting a run.
Library errors expose message, suggested_agent_action and to_dict().
InvalidInputError is also a ValueError for existing handlers. For example:
from hirepulse_tools import HirePulseError, company_intent
try:
items = company_intent(["stripe.com"], result_limit=5, max_total_charge_usd=0.10)
except HirePulseError as error:
print(error.to_dict()) # Safe message and suggested_agent_action; no token or raw SDK text
MCP failures set isError=true and include
{"error": {"message": "...", "suggested_agent_action": "..."}} in both JSON
text and structured content. This includes argument validation and unknown-tool
errors. Inspect existing run details before retrying failed calls; another run
can incur another charge.
Local MCP exposes the same eight names and inputs. Each response is a JSON text
envelope with items, returned_items, omitted_items, output_truncated,
result_limit_reached and note, limited to 32,000 UTF-8 bytes. Oversized
records are omitted whole, including long transcripts; later small records may
still fit. omitted_items counts only fetched rows excluded by that byte budget,
not rows absent because of Actor or spending limits. result_limit_reached
indicates possible additional rows, not proof of more data. Use the Python
library when you need full large records. External results are data, not agent
instructions. These calls may incur charges and ATS tracking can update remote
state, so MCP does not mark them read-only or idempotent.
Prices below come only from the supplied FACTS.md snapshot dated 2026-10-15.
Higher Apify plans get volume discounts. No price is stated for ATS Job Scraper,
Domain SEO Overview or YouTube Transcript Scraper because that facts sheet
does not specify one.
| Tool | Price |
|---|---|
| AliExpress Search Scraper | $2.50 per 1,000 products |
| Google Ads Transparency Scraper | $0.005 per domain + $0.0015 per ad |
| Company Intent Radar | $0.03 per company report, charged only when the full report was produced |
| Google Jobs Scraper | $0.005 per search that returns jobs + $0.001 per job |
| Keyword Search Volume | $0.03 per lookup + $0.005 per keyword result |
These limits come from the same facts sheet:
posted_at and
posted_ago.python -m pip install -e ".[dev]"
python -m pytest -q
Dependency installation may need network access; the tests do not. Tests mock
apify-client, block real Actor starts and HTTP calls, and check every input
schema, defaults, cap forwarding, missing-token errors, failure handling and all
eight MCP tools. No token or live Actor is needed. Python 3.11.9 was used for
the supplied verification; Python 3.10 has not been run for this handoff.
The bundled input/output schema snapshots were copied unchanged from the local facts. Output schemas describe dataset/run-summary links rather than complete row schemas, so this library deliberately returns untyped row dictionaries. Product descriptions use only the supplied facts and tool schemas/READMEs; example output measurements and older reference prices were not copied.
SKILL.md explains tool selection, exact Actor IDs, inputs and output fields. AGENTS.md covers working on this repository.
The directory files are local drafts for human review: server.json describes
hosted MCP and the stdio Python package, glama.json lists maintainers, and
smithery.yaml maps the required secret apifyToken to APIFY_TOKEN. Install
.[mcp] before using Smithery's python -m hirepulse_tools.mcp_server command.
No directory submission, package publication or hosted deployment has occurred.
Edit GitHub identity only in publishing.json, then run
python scripts/render_metadata.py. The generated registry name, repository URL,
Glama maintainer and README ownership marker use that single source. Literal
copies in directory files are required by their formats; do not edit them by
hand. Run python scripts/render_metadata.py --check to detect drift. Release
name/version come from pyproject.toml.
The registry package command is intended for a future published release:
uvx --from 'hirepulse-tools[mcp]==0.1.0' hirepulse-mcp. For this checkout use
the local installation instructions above. Schema validation does not verify
directory acceptance, namespace/package ownership or live hosted authentication.
See directory format sources and validation.
MIT.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
uvx hirepulse-toolsMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-edtool79-collab-hirepulse-open-source": {
"command": "uvx",
"args": [
"hirepulse-tools"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceHirePulse tools works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.