Skip to main content
Glama
AdvaitR7

Firecrawl MCP Multiple Keys

by AdvaitR7

firecrawl_interact

Execute multi-step interactions on a live web page: click, fill forms, and extract dynamic content within one browser session.

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
Behavior4/5

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

The description mentions opening a live session, reuse option, and return types (output, stdout, stderr, exit code, live view URLs). Annotations indicate readOnlyHint=false and openWorldHint=true, and the description aligns with this. It adds context about cost savings when reusing scrapeId. However, it does not disclose session lifecycle or cleanup details.

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

Conciseness4/5

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

The description is organized with clear sections and bullet-like arguments, making it easy to scan. It is somewhat lengthy but every sentence adds value. The front-loading of purpose and best-for is effective. Examples are useful.

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

Completeness3/5

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

Given the complexity (7 params, nested scrapeOptions, no output schema), the description covers core functionality well but omits details on error handling, session persistence, and the exact structure of the return object beyond a brief mention. The sibling tool 'firecrawl_interact_stop' suggests a stop capability not referenced here.

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

Parameters4/5

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

With 0% schema description coverage, the description compensates well by explaining each parameter's purpose and constraints (e.g., url vs scrapeId mutual exclusivity, prompt vs code alternatives, timeout range, language defaults). It also gives examples. However, scrapeOptions is only partially described with examples, not fully covering all nested properties.

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 it interacts with a page in a live browser session using verbs like click, fill, extract. It distinguishes from siblings by specifically mentioning reuse of scrapeId from previous scrape, which is a key differentiator from tools like firecrawl_scrape.

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

Usage Guidelines4/5

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

The description explicitly labels 'Best for: Multi-step workflows' and explains two targeting methods (url vs scrapeId). However, it does not explicitly contrast with similar sibling tools like firecrawl_agent or firecrawl_scrape, leaving some ambiguity for the agent to infer.

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/AdvaitR7/firecrawl-mcp-multiple-keys'

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