Building permits from 18 US cities (NYC, LA, Chicago, Philadelphia...), Canada, Ireland, France.
Scored across 5 tools
The tools mostly target distinct resources and actions, but the actor-specific tool overlaps with get-dataset-items because both appear to retrieve Actor output/results. The actor-specific tool's opaque name also makes its boundary less immediately clear than the generic run/data tools.
Four tools follow a readable kebab-case verb-noun pattern, but the fifth tool is an actor identifier with a double hyphen and no verb. The mix is still decipherable, though it breaks the otherwise predictable naming scheme.
Five tools is compact and within a reasonable range for a focused server. However, four tools are generic Apify infrastructure while only one is building-permits-specific, leaving the set slightly imbalanced for a server named building-permits-api.
The core read-only workflow is present: call the permit-data actor, inspect or abort its run, fetch dataset rows, and read a key-value record. Still, there are notable gaps for a permits API, including no explicit permit search/filter operation and no listing operations for datasets, key-value keys, or runs.
Abort an Actor run that is currently starting or running. For runs with status SUCCEEDED, FAILED, ABORTING, ABORTED, or TIMED-OUT, this call has no effect. The results will include the updated run details after the abort request.
USAGE:
Use when you need to stop a run that is taking too long or misconfigured.
USAGE EXAMPLES:
user_input: Abort run y2h7sK3Wc
user_input: Gracefully abort run y2h7sK3Wc
Inputs: runId (required), gracefully. Returns: tip, runId, stats, status, +10 more
This tool calls the Actor "gaelasao/planning-data-au-nz-fr" and retrieves its output results. Actor description: Building permit data from 18 US cities (NYC, Los Angeles, Chicago, Philadelphia, Dallas, Pittsburgh, Orlando…): construction permits with value and contractor. Contractor leads, roofing leads and solar leads. Ireland planning applications, France permis de construire, NSW development applications.
Inputs: dateTo, country, onlyNew, councils, +11 more. Returns: tip, runId, stats, status, +10 more
Get detailed information about a specific Actor run.
Returns run result: status, storages (datasets/keyValueStores alias map), stats, summary, nextStep.
summary describes the past (e.g. "SUCCEEDED in 22s. 47 items; 3 fields available.").
nextStep prescribes one primary follow-up action with identifiers interpolated (e.g. "Use get-dataset-items with datasetId=...").
waitSecs (0–45, default 30) waits up to that many seconds for terminal status before returning.
USAGE:
Use to check the status of a run started by any Actor-running tool.
Pass waitSecs > 0 to block until terminal (or until the cap elapses).
USAGE EXAMPLES:
user_input: Show details of run y2h7sK3Wc
user_input: Wait for run y2h7sK3Wc to finish
Inputs: runId (required), waitSecs. Returns: tip, runId, stats, status, +10 more
Get items (rows) from a dataset — the output/results produced by an Actor run. Returns the rows themselves, not dataset metadata, counts, or a schema. When the user provides a datasetId and asks to retrieve results, output, data, or rows, call this tool directly. Default limit is 20. Use clean=true to skip empty items and hidden fields.
USAGE:
Use when you need to read data from a dataset (all items or only selected fields).
USAGE EXAMPLES:
user_input: Retrieve results from dataset abc123
user_input: Get only metadata.url and title from dataset username~my-dataset
Inputs: datasetId (required), desc, omit, clean, +4 more. Returns: items, limit, offset, summary, +5 more
Get the value stored under a specific key in a key-value store — a single record, not a listing of all keys. Requires the exact key name. The response preserves the original Content-Encoding; most clients handle decompression automatically.
USAGE:
Use when you need to retrieve a specific record (JSON, text, or binary) from a store.
USAGE EXAMPLES:
user_input: Get record INPUT from store abc123
user_input: Get record data.json from store username~my-store
Inputs: recordKey (required), keyValueStoreId (required). Returns: key, value, summary, contentType, +1 more
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Building permits by address for a growing list of US cities and counties, from city open data.
U.S. building permits, permit histories by address and contractors from city and county records.
Fresh US building permits with contacts from official city APIs. Construction lead generation.
US parcels and building permits from public sources. No owner data. Pay per record or monthly plan.
Add one secure layer between your agents and this server.