Skip to main content
Glama
firecrawl

firecrawl-mcp-server

firecrawl_interact

Perform actions on web pages in a live browser session using natural language prompts or code. Click, fill forms, extract dynamic content, and navigate through multi-step workflows.

Instructions

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 page (cheaper when you just scraped it).

Arguments:

  • url: Page to interact with; opens a session for you (use this OR scrapeId)

  • scrapeId: Scrape job ID from a previous scrape, found in its metadata (use this OR url)

  • prompt: Natural language instruction describing the action to take (use this OR code)

  • code: Code to execute in the browser session (use this OR prompt)

  • language: "bash", "python", or "node" (optional, defaults to "node", only used with code)

  • timeout: Interact execution timeout in seconds, 1-300 (optional, defaults to 30)

  • scrapeOptions: Optional scrape controls used only with url mode, such as waitFor, maxAge, proxy, or zeroDataRetention

Usage Example (prompt, direct via url):

{
  "name": "firecrawl_interact",
  "arguments": {
    "url": "https://example.com/products",
    "prompt": "Click on the first product and tell me its price"
  }
}

Usage Example (code):

{
  "name": "firecrawl_interact",
  "arguments": {
    "scrapeId": "scrape-id-from-previous-scrape",
    "code": "agent-browser click @e5",
    "language": "bash"
  }
}

Returns: Execution result including output, stdout, stderr, exit code, and live view URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
codeNo
promptNo
timeoutNo
languageNo
scrapeIdNo
scrapeOptionsNo
Behavior5/5

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

Beyond annotations (readOnlyHint=false, destructiveHint=false), the description details behavioral traits: it opens a live browser session, allows interaction (clicking, filling forms), reuses sessions via scrapeId, and returns execution results including stdout, stderr, exit code, and live view URLs. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured: purpose, best for, two modes, argument list, examples, returns. It is concise yet comprehensive, front-loading key information. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema and complex nested parameters (scrapeOptions), the description covers all parameters, provides usage examples, and explains the return structure. It gives enough context for an AI agent to correctly invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has no descriptions (0% coverage), but the description thoroughly explains each parameter in the 'Arguments' section, including mutual exclusivity (url vs scrapeId, prompt vs code), language options, timeout range, and scrapeOptions usage. This adds significant meaning beyond the schema.

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

Purpose5/5

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

The description clearly states the tool's purpose: 'Interact with a page in a live browser session: click buttons, fill forms, extract dynamic content, or navigate deeper.' It uses a specific verb and resource and distinguishes itself from siblings like firecrawl_scrape by emphasizing multi-step workflows.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use the tool ('Best for: Multi-step workflows on a single page') and explains two targeting modes (url vs scrapeId) with different use cases. It implicitly excludes single-step scraping, suggesting firecrawl_scrape for that.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/firecrawl/firecrawl-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server