AIsa Web Search & Research

Firecrawl Map

post_firecrawl_map

Destructive

Usage-based billing; Default request estimate: $0.001071 USD (not a fixed price). Declared unit rate: $0.001071 USD per firecrawl_credit. Account-specific pricing and final settlement may differ.

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": {
      "body": "<body>"
    },
    "name": "post_firecrawl_map"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 19, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / body

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "limit": {
+      "maximum": 100000,
+      "minimum": 1,
+      "type": "integer"
+    },
+    "url": {
+      "format": "https_url",
+      "type": "string"
+    }
+  },
+  "required": [
+    "limit",
+    "url"
+  ],
+  "type": "object"
+}

removedInput schema / properties / limit

Removed value: -{
-  "maximum": 100000,
-  "minimum": 1,
-  "type": "integer"
-}

removedInput schema / properties / url

Removed value: -{
-  "format": "https_url",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "limit",
-  "url"
-]New value: +[
+  "body"
+]

Changed6 schema fields changedOct 15, 2026

removedInput schema / properties / limit / description

Removed value: -"Maximum number of links to discover. Required on the metered profile."

removedInput schema / properties / limit / example
```
Removed value: -100
```
removedInput schema / properties / url / description
```
Removed value: -"The HTTPS URL to map."
```
removedInput schema / properties / url / example
```
Removed value: -"https://docs.firecrawl.dev"
```

changedInput schema / properties / url / format

Previous value: -"uri"New value: +"https_url"

changedInput schema / required

Previous value: -[
-  "url",
-  "limit"
-]New value: +[
+  "limit",
+  "url"
+]

Changed6 schema fields changedOct 15, 2026

addedInput schema / properties / limit / description

Added value: +"Maximum number of links to discover. Required on the metered profile."

addedInput schema / properties / limit / example
```
Added value: +100
```
addedInput schema / properties / url / description
```
Added value: +"The HTTPS URL to map."
```
addedInput schema / properties / url / example
```
Added value: +"https://docs.firecrawl.dev"
```

changedInput schema / properties / url / format

Previous value: -"https_url"New value: +"uri"

changedInput schema / required

Previous value: -[
-  "limit",
-  "url"
-]New value: +[
+  "url",
+  "limit"
+]

Changed6 schema fields changedOct 15, 2026

removedInput schema / properties / limit / description

Removed value: -"Maximum number of links to discover. Required on the metered profile."

removedInput schema / properties / limit / example
```
Removed value: -100
```
removedInput schema / properties / url / description
```
Removed value: -"The HTTPS URL to map."
```
removedInput schema / properties / url / example
```
Removed value: -"https://docs.firecrawl.dev"
```

changedInput schema / properties / url / format

Previous value: -"uri"New value: +"https_url"

changedInput schema / required

Previous value: -[
-  "url",
-  "limit"
-]New value: +[
+  "limit",
+  "url"
+]

First observedSep 15, 2026

TDQS

D1.1/5.0

Behavior1/5

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

Annotations declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true, but the description discloses nothing about behavior, side effects, permissions, or rate limits. The only content is pricing boilerplate, which does not add any behavioral context beyond the annotations.

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

Conciseness2/5

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

The text is short, but every word is pricing boilerplate that does not help select or invoke the tool. Brevity here reflects absent content rather than efficient communication of the tool's purpose.

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

Completeness1/5

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

For a destructive, open-world POST tool with a nested object parameter and zero schema descriptions, the description supplies none of the required context. An output schema exists, so return values need not be explained, but purpose, usage, and parameter meaning are all missing.

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

Parameters1/5

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

The single nested body parameter (with url and limit) has 0% schema description coverage, so the description must compensate and does not. It gives no hint about what url or limit mean, valid ranges, or expected formats, leaving the parameter effectively undocumented everywhere.

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

Purpose1/5

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

The description never states what the tool does. It contains only billing metadata ('Usage-based billing; Default request estimate: $0.001071 USD'), which is a pricing note rather than a purpose statement. The agent must infer the function purely from the name 'post_firecrawl_map'.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no mention of alternatives such as post_tavily_map, post_firecrawl_crawl, or post_firecrawl_scrape, and no preconditions. Nothing in the text helps an agent decide between this tool and its numerous siblings.

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

All AIsa Web Search & Research tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?