Nimble

List pre-built agent templates that can seed nimble_agents_create(template=...).

nimble_agent_templates_list

List web search agents in the account. Typical workflow: list → get (inspect) → run (start a research run) → run_status (poll) → run_result (fetch output).

nimble_agents_list

Browse the catalog of extract templates. Use this tool as the first step to find an existing template for a data collection task. Each template is purpose-built for a specific website or data type (e.g. Amazon products, LinkedIn profiles, Google Maps reviews). Typical workflow: list → get (inspect details) → run (collect data).

nimble_extract_templates_list

List crawl jobs, optionally filtered by status.

nimble_crawl_list

Start a web crawl to extract content from multiple pages on a website. The crawl discovers and visits pages starting from the given URL, following links up to the specified limit. Results can be retrieved via nimble_crawl_status. Latency & when to use: Asynchronous and cold-start-bound. This call returns a crawl_id immediately, but the job is queued: the first pages typically don't begin completing until ~1-2 minutes after dispatch, and total time scales with `limit`. Poll `nimble_crawl_status` for progress. Use this only when you need many pages from a site discovered and extracted automatically — it is the slowest of the extraction paths to first result. For a single known URL you want inline, use `nimble_extract`; for one URL where you can wait and poll, use `nimble_extract_async`.

nimble_crawl_run

Check the status and progress of a running or completed crawl job.

nimble_crawl_status

Cancel a running or queued crawl job.

nimble_crawl_terminate

Extract and parse content from a specific URL using Nimble's Extract API. This tool fetches and extracts clean, structured content from any web page. Use when you have a specific URL and need its full content. Latency & when to use: Synchronous — returns the content in this single call. Typical latency is sub-second to a few seconds for standard pages, so this is the default choice for a single URL you need inline right now. JavaScript-heavy or single-page-app pages take longer to render and can run up to the tool-call timeout configured by your MCP client (commonly ~180s) (especially when `wait` is set); a page that requires a login or returns a consent/interstitial prompt may yield little or no content. If you have many URLs to extract, or your turn's latency budget can't absorb a slow page, use `nimble_extract_async` instead. For discovering and pulling many pages across a whole site, use `nimble_crawl_run`.

nimble_extract

Start an asynchronous URL extraction. Returns immediately with a task ID. Use this for batch processing or when you don't need results immediately. Retrieve results later with nimble_task_results using the returned task ID. Latency & when to use: This call returns a task ID in sub-second time, but the extraction itself runs out-of-band: a single URL typically takes ~30s end-to-end before results are ready (queueing and dispatch overhead make the async path an order of magnitude slower than the synchronous `nimble_extract` on comparable pages — it is not a faster route to the same content). After starting, poll `nimble_task_results` with the returned task ID, or supply `callback_url` to be notified on completion. Prefer this path when extracting many URLs in parallel, or when a single synchronous call would blow your turn's latency budget. For one URL you need inline now, use `nimble_extract`. For crawling many pages across a site, use `nimble_crawl_run`.

nimble_extract_async

Start an asynchronous extract template run. Returns immediately with a task ID. Use this for long-running template extractions or batch processing. Retrieve results later with nimble_task_results using the returned task ID.

nimble_extract_templates_run_async

Discover all URLs on a website by crawling its pages and sitemap. Returns a flat list of URLs found on the site. Useful for understanding site structure before targeted extraction or crawling.

nimble_map

Search the web using Nimble's Search API with configurable content richness. This tool provides comprehensive web search capabilities across multiple sources and formats. Use for research, fact-checking, finding sources, or gathering current information.

nimble_search

Get the status and results of an async task. Use this to retrieve results from nimble_extract_async or nimble_extract_templates_run_async. If the task is still pending, returns the current state so you can poll again later.

nimble_task_results

Create a refinement generation that starts from an existing extract template. Returns a ``generation_id``; poll progress via nimble_extract_templates_generation_status until terminal. On success, use the returned ``template_name`` with nimble_extract_templates_run.

nimble_extract_templates_update_from_template

Execute an extract template against a target URL or set of parameters. Returns structured data collected from the target page. The params dict must match the template's input_schema — use nimble_extract_templates_get to inspect required fields. Possible issues if no results are returned: - The target URL may be unreachable or behind a login wall. - The page structure may have changed since the template was created. - Required params may be missing or malformed — check the template's input_schema.

nimble_extract_templates_run

Start an asynchronous agent run. Returns immediately with a run ``id`` and ``status``. Poll nimble_agents_run_status until the status is terminal, then fetch the output via nimble_agents_run_result.

nimble_agents_run

Update an existing agent via JSON Patch operations.

nimble_agents_update