Skip to main content
Glama

Firecrawl by Nova (CIVAI)

firecrawl_interact

Open or reuse a live browser session to navigate a page, click controls, fill and submit forms, or run browser code. Provide either url (the scheme may be omitted) or scrapeId, and either a natural-language prompt or executable code; code can run as Bash, Python, or Node with a bounded timeout.

The session runs in an isolated Firecrawl-hosted browser that never receives the end user's own browser cookies or credentials. By default it starts with no cookies or saved sessions; an optional team-scoped scrapeOptions.profile reuses state saved by the team's earlier sessions. Actions run on the live site, so submitting a form can have effects on that site. Returns execution output, stdout/stderr, exit status, and session viewing URLs. When the page needs the user to act, share interactiveLiveViewUrl with the user only, so they can take over the session.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "firecrawl_interact"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
codeNo
promptNo
timeoutNo
languageNo
scrapeIdNo
objectiveNoThe user's underlying goal in one sentence, not a restatement of this call's arguments. Reuse it across related calls. Firecrawl uses it to learn what agents need and improve its results. No personal data, secrets or the user's exact words.
scrapeOptionsNo
conversationIdNoconversationId from any earlier Firecrawl tool result in this conversation; after parallel calls, any one of theirs. Omit only on the first call of a conversation; the result returns one to pass on every later call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / objective
      Added value: +{
      +  "description": "The user's underlying goal in one sentence, not a restatement of this call's arguments. Reuse it across related calls. Firecrawl uses it to learn what agents need and improve its results. No personal data, secrets or the user's exact words.",
      +  "maxLength": 5000,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • removedInput schema / properties / url / format
      Removed value: -"uri"
  3. Changed1 schema field changed
    • changedInput schema / properties / scrapeOptions / properties / jsonOptions / properties / schema / additionalProperties
      Previous value: -{}New value: +true
  4. First observed

TDQS

A4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses isolation from the end user's cookies/credentials, that sessions start empty unless a team profile is reused, that actions hit the live site and can have real effects, and what the result contains (execution output, stdout/stderr, exit status, viewing URLs). It even adds a privacy instruction to share interactiveLiveViewUrl only with the user.

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?

Two paragraphs, front-loaded with capability then constraints and safety notes. Dense but nearly every sentence adds information; only the viewing-URL sentence could be trimmed slightly for narrative flow.

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

Completeness4/5

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

For a 9-parameter interactive tool with no output schema and no annotations, the description covers isolation model, state persistence, side effects, and return shape. Minor gaps remain on session lifetime and teardown (the stop sibling) but nothing critical is missing for correct invocation.

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?

Schema coverage is only 22%, but the description compensates for the parameters that matter by explaining the url/scrapeId alternation, the prompt/code alternation, supported code languages and bounded timeout, and the team-scoped profile reuse semantics. It leaves objective and conversationId, plus most nested scrapeOptions fields, to the schema.

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

Purpose4/5

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

States a specific verb and resource ('Open or reuse a live browser session') and enumerates concrete capabilities: navigate, click, fill and submit forms, run browser code. An agent can distinguish this from firecrawl_scrape because it mentions an interactive session, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Gives construction guidance ('Provide either url or scrapeId, and either a natural-language prompt or executable code') and a caution about when submission affects the live site, which implies when to use prompt vs code. It never states when to prefer this over firecrawl_scrape or when to stop with firecrawl_interact_stop, so routing is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources