Firecrawl MCP Server

Stop Firecrawl interact session

firecrawl_interact_stop

Destructive

Stop a live interact session by scrapeId and release its resources, returning a success confirmation when the session is closed.

Instructions

Stop the live interact session associated with a scrapeId and release its resources. Returns a success confirmation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "scrapeId": "<scrapeId>"
    },
    "name": "firecrawl_interact_stop"
  }
}

Input Schema

Name	Required	Description	Default
`scrapeId`	Yes

Output Schema

Name	Required	Description
`error`	No	Error message or error object when the call did not succeed.
`message`	No	Confirmation that the session was stopped.
`success`	No	Whether the API call succeeded.
`scrapeId`	No	Session that was stopped.
`agent_hints`	No	Optional response guidance from the Firecrawl API.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.28.2Nov 4, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this is a mutating call; the description adds the useful nuance that the session's resources are released. However, it says nothing about idempotency, behavior when the `scrapeId` is unknown or the session already stopped, or whether any error is raised — gaps that matter for a destructive teardown.

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?

Two short sentences with the action and its effect front-loaded, and the return-value note deferred to the end. No redundant or filler wording.

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?

An output schema exists, so the description need not detail return values, and it correctly stays brief for a one-parameter tool. What is missing for a destructive session-teardown tool is error/edge-case behavior (missing session, repeat calls) and the linkage to `firecrawl_interact` that created the session.

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

Parameters3/5

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

Schema description coverage is 0% and the single `scrapeId` parameter is undocumented in the schema. The description only implies it identifies the live session to stop; it does not say whether it is the id returned by `firecrawl_interact`, what format it takes, or what happens if it refers to an expired session.

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?

The description uses a specific verb and resource ("Stop the live interact session") and ties it to a `scrapeId`, which lets an agent pair it against the sibling `firecrawl_interact` without opening either schema. It stops short of naming that sibling explicitly, so it is clear but not fully differentiated in text.

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?

"Stop the live interact session ... and release its resources" implies the use case (tearing down a session to free resources), but there is no explicit when-to-use/when-not guidance, no mention that a session must first be created via `firecrawl_interact`, and no alternative to consider.

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