fxdesign

Showing 25 of 26 from the live probe.

• Firecrawl Scrape

  Scrape content from a single URL with advanced options. This is the most powerful, fastest and most reliable scraper tool, if available you should always default to using this tool for any web scraping needs. **Best for:** Single page content extraction, when you know exactly which page contains the information. **Not recommended for:** Multiple pages (call scrape multiple times or use crawl), unknown page location (use search). **Common mistakes:** Using markdown format when extracting specifi

• Firecrawl Map

  Map a website to discover all indexed URLs on the site. **Best for:** Discovering URLs on a website before deciding what to scrape; finding specific sections or pages within a large site; locating the correct page when scrape returns empty or incomplete results. **Not recommended for:** When you already know which specific URL you need (use scrape); when you need the content of the pages (use scrape after mapping). **Common mistakes:** Using crawl to discover URLs instead of map; jumping straig

• Firecrawl Search

  Search the web and optionally extract content from search results. This is the most powerful web search tool available, and if available you should always default to using this tool for any web search needs. The query also supports search operators, that you can use if needed to refine the search: | Operator | Functionality | Examples | ---|-|-| | `"` | Non-fuzzy matches a string of text | `"Firecrawl"` | `-` | Excludes certain keywords or negates other operators | `-bad`, `-site:firecrawl.dev`

• Firecrawl Search Feedback

  Send structured feedback on a previous `firecrawl_search` result. **Call this immediately after a search where you used the results** so we can improve search quality and refund 1 credit (search costs 2). Pass the `searchId` returned by `firecrawl_search` (the `id` field on the response) and tell us: - **rating** — overall result quality: `good`, `partial`, or `bad`. - **valuableSources** — which result URLs were actually useful, and a short reason why. - **missingContent** — **the most import

• Firecrawl Feedback

  Send structured feedback for a completed Firecrawl v2 job. Use this for endpoint-level feedback on `scrape`, `parse`, `map`, or `search` jobs when the job result was useful, partially useful, or failed to meet expectations. For search-result quality specifically, prefer `firecrawl_search_feedback` when available because it has search-focused guidance. This generic tool posts to `/v2/feedback` and accepts endpoint-wide signals: - **endpoint** — one of `search`, `scrape`, `parse`, or `map`. - **

• Firecrawl Crawl

  Starts a crawl job on a website, polls until it reaches a terminal state, and returns the final crawl status/data. **Best for:** Extracting content from multiple related pages, when you need comprehensive coverage. **Not recommended for:** Extracting content from a single page (use scrape); when token limits are a concern (use map + scrape for tighter control); when you need fast results (crawling can be slow). **Warning:** Crawl responses can be very large and may exceed token limits. Limi

• Firecrawl Check Crawl Status

  Check the status of a crawl job. **Usage Example:** ```json { "name": "firecrawl_check_crawl_status", "arguments": { "id": "550e8400-e29b-41d4-a716-446655440000" } } ``` **Returns:** Status and progress of the crawl job, including results if available.

• Firecrawl Extract

  Extract structured information from web pages using LLM capabilities. Supports both cloud AI and self-hosted LLM extraction. **Best for:** Extracting specific structured data like prices, names, details from web pages. **Not recommended for:** When you need the full content of a page (use scrape); when you're not looking for specific structured data. **Arguments:** - urls: Array of URLs to extract information from - prompt: Custom prompt for the LLM extraction - schema: JSON schema for structur

• Firecrawl Agent

  Autonomous web research agent. This is a separate AI agent layer that independently browses the internet, searches for information, navigates through pages, and extracts structured data based on your query. You describe what you need, and the agent figures out where to find it. **How it works:** The agent performs web searches, follows links, reads pages, and gathers data autonomously. This runs **asynchronously** - it returns a job ID immediately, and you poll `firecrawl_agent_status` to check

• Firecrawl Agent Status

  Check the status of an agent job and retrieve results when complete. Use this to poll for results after starting an agent with `firecrawl_agent`. **IMPORTANT - Be patient with polling:** - Poll every 15-30 seconds - **Keep polling for at least 2-3 minutes** before considering the request failed - Complex research can take 5+ minutes - do not give up early - Only stop polling when status is "completed" or "failed" **Usage Example:** ```json { "name": "firecrawl_agent_status", "arguments": {

• Firecrawl Interact

  Interact with a page in a live browser session: click buttons, fill forms, extract dynamic content, or navigate deeper. **Best for:** Multi-step workflows on a single page — searching a site, clicking through results, filling forms, extracting data that requires interaction. **Two ways to target a page:** - Pass a `url` to interact directly. The session is opened for you in one call (use this for a fresh page). - Pass a `scrapeId` from a previous firecrawl_scrape to reuse that already-loaded pa

• Firecrawl Interact Stop

  Stop an interact session for a scraped page. Call this when you are done interacting to free resources. **Usage Example:** ```json { "name": "firecrawl_interact_stop", "arguments": { "scrapeId": "scrape-id-here" } } ``` **Returns:** Success confirmation.

• Firecrawl Parse

  Parse a file using Firecrawl's /v2/parse endpoint. In local/non-cloud MCP mode, this tool reads filePath from the MCP server filesystem and posts multipart data to the configured self-hosted FIRECRAWL_API_URL, preserving the existing direct-read behavior. In hosted CLOUD_SERVICE mode, this tool is a two-call flow because hosted MCP cannot read your local filesystem: 1. Call with filePath, contentType, parse options, and optional declaredSizeBytes. The hosted server mints a short-lived upload U

• Firecrawl Monitor Create

  Create a Firecrawl monitor — a recurring scrape, crawl, or search that diffs each result against the last retained snapshot. Prefer the simple path: pass `page` or `pages` plus `goal` to monitor specific URLs, OR pass `queries` plus `goal` to monitor web search results for new/changed hits. The tool will create the monitor with a 30-minute schedule and meaningful-change judging enabled by the API. Use `body` only for advanced requests such as crawl targets, JSON change tracking, custom retentio

• Firecrawl Monitor List

  List all Firecrawl monitors for the authenticated account. **Usage Example:** ```json { "name": "firecrawl_monitor_list", "arguments": { "limit": 20 } } ```

• Firecrawl Monitor Get

  Get a single monitor by ID. **Usage Example:** ```json { "name": "firecrawl_monitor_get", "arguments": { "id": "mon_abc123" } } ```

• Firecrawl Monitor Update

  Update a monitor. Pass any subset of fields to patch: `name`, `status` ("active" | "paused"), `schedule`, `targets`, `goal`, `judgeEnabled`, `webhook`, `notification`, `retentionDays`. **Usage Example:** ```json { "name": "firecrawl_monitor_update", "arguments": { "id": "mon_abc123", "body": { "status": "paused" } } } ```

• Firecrawl Monitor Delete

  Permanently delete a monitor and stop its schedule. This cannot be undone. **Usage Example:** ```json { "name": "firecrawl_monitor_delete", "arguments": { "id": "mon_abc123" } } ```

• Firecrawl Monitor Run

  Trigger a monitor check immediately, outside its normal schedule. Returns the queued check. **Usage Example:** ```json { "name": "firecrawl_monitor_run", "arguments": { "id": "mon_abc123" } } ```

• Firecrawl Monitor Checks

  List historical checks for a monitor. **Usage Example:** ```json { "name": "firecrawl_monitor_checks", "arguments": { "id": "mon_abc123", "limit": 10, "status": "completed" } } ```

• Firecrawl Monitor Check

  Get a single check with page-level diff results. Filter `pageStatus` to surface only the pages that changed (or were new, removed, etc.). Each entry in `data.pages[]` has `url`, `status` (`same` | `new` | `changed` | `removed` | `error`), optional `judgment` when goal-based judging ran, and — when changed — a `diff` and possibly a `snapshot`. The shape of `diff` depends on the monitor's `formats` configuration: - **Markdown mode (default).** `diff.text` is the unified markdown diff; `diff.json

• Firecrawl Research Search Papers

  Primary entry point for finding research papers by topic across AI/ML, computer science, math, physics, biomedical, life sciences, and clinical literature. Semantic (HyDE) search over indexed paper metadata and abstracts; returns ranked papers with paper id, title, authors, and abstract. The query should be a natural-language research topic or question. Run SEVERAL distinct framings of the question (sibling domains, rival methods, dataset or benchmark names, conditions, populations, intervention

• Firecrawl Research Inspect Paper

  Fetch canonical metadata for one paper by primaryId or canonical paperId. Use this after search/related results when you need the full title, abstract, authors, categories, source ids, and dates rendered as markdown.

• Firecrawl Research Related Papers

  Expand from anchor papers you have already found, via the citation graph, ranked and filtered to a natural-language `intent`. Pass arXiv ids of your strongest hits as `seed_ids`. Modes: `similar` (cocitation/coupling — papers in the same niche; the default), `citers` (papers that cite the anchors), `references` (papers the anchors cite). This reaches relevant papers that plain search misses, so use it on your best hits before finishing. A `similar` call already runs a DEEP multi-round expansion

• Firecrawl Research Read Paper

  Read the most relevant in-body (full-text) passages of ONE specific paper for a question. Use this to VERIFY whether a candidate actually satisfies a constraint before you include or reject it (e.g. 'does this paper actually use technique X / report a score on benchmark Y'). Returns the best-matching passages, or a notice if the paper's full text is unavailable.