Firecrawl MCP Server

Overview Schema Source Related Servers Discussions Admin

Stop Firecrawl interact session

firecrawl_interact_stop

DestructiveIdempotent

Terminates a live browser interaction session for a given scrapeId, releasing associated resources and returning a success confirmation.

Instructions

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

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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.2Oct 29, 2026

changedInput schema / $schema

Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "description": "Confirmation that the interact session was stopped.",
+  "properties": {
+    "error": {
+      "description": "Error message or error object when the call did not succeed."
+    },
+    "message": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Confirmation that the session was stopped."
+    },
+    "scrapeId": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Session that was stopped."
+    },
+    "success": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Whether the API call succeeded."
+    }
+  },
+  "type": "object"
+}

First observedv1.0.1Jul 5, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds that resources are released and a success confirmation is returned, which is consistent with (not contradictory to) the destructive flag, but it omits auth requirements and the behavior on an expired/unknown scrapeId.

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, zero filler, with the action and its resource front-loaded before the return-value note. Nothing here is redundant padding.

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 single-parameter teardown call with a declared output schema and full annotation coverage, the description supplies everything essential. Minor gaps: no error/unknown-session behavior and no note on whether subsequent interact calls on the same scrapeId require a restart.

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% for the single parameter, so the description must compensate. It does clarify the key semantic point — the scrapeId identifies the live session to terminate rather than a document to fetch — but gives no format, prefix, or validation detail.

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?

Specific verb ('Stop') plus specific resource ('live interact session') scoped to a scrapeId. The pairing with the sibling firecrawl_interact is strongly implied by the naming and the 'live session' framing, though the description never names the sibling 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?

Usage is only implied: an agent infers this is the teardown call after an interact session is no longer needed. There is no explicit 'call this when…' guidance, no note about what happens if the session is already closed, and no stated alternative.

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