Skip to main content
Glama

AIsa Web Search & Research

by one.aisa
OverviewDiscussionsAdmin

Firecrawl Search

post_firecrawl_search
Destructive

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

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / body
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "enterprise": {
+      "default": false,
+      "enum": [
+        false
+      ],
+      "type": "boolean"
+    },
+    "limit": {
+      "default": 10,
+      "maximum": 100,
+      "minimum": 1,
+      "type": "integer"
+    },
+    "query": {
+      "maxLength": 2000,
+      "minLength": 1,
+      "type": "string"
+    },
+    "sources": {
+      "default": [
+        "web"
+      ],
+      "enum": [
+        [
+          "web"
+        ]
+      ],
+      "items": {
+        "type": "string"
+      },
+      "maxItems": 1,
+      "minItems": 1,
+      "type": "array"
+    }
+  },
+  "required": [
+    "query"
+  ],
+  "type": "object"
+}
    • removedInput schema / properties / enterprise
      Removed value: -{
-  "default": false,
-  "enum": [
-    false
-  ],
-  "type": "boolean"
-}
    • removedInput schema / properties / limit
      Removed value: -{
-  "default": 10,
-  "maximum": 100,
-  "minimum": 1,
-  "type": "integer"
-}
    • removedInput schema / properties / query
      Removed value: -{
-  "maxLength": 2000,
-  "minLength": 1,
-  "type": "string"
-}
    • removedInput schema / properties / sources
      Removed value: -{
-  "default": [
-    "web"
-  ],
-  "enum": [
-    [
-      "web"
-    ]
-  ],
-  "items": {
-    "type": "string"
-  },
-  "maxItems": 1,
-  "minItems": 1,
-  "type": "array"
-}
    • changedInput schema / required
      Previous value: -[
-  "query"
-]New value: +[
+  "body"
+]
  2. Changed7 schema fields changed
    • addedInput schema / properties / enterprise
      Added value: +{
+  "default": false,
+  "enum": [
+    false
+  ],
+  "type": "boolean"
+}
    • removedInput schema / properties / limit / description
      Removed value: -"Maximum number of results to return."
    • removedInput schema / properties / query / description
      Removed value: -"The search query. Must be non-empty and at most 500 characters."
    • removedInput schema / properties / query / example
      Removed value: -"firecrawl web scraping api"
    • changedInput schema / properties / query / maxLength
      Previous value: -500New value: +2000
    • addedInput schema / properties / query / minLength
      Added value: +1
    • addedInput schema / properties / sources
      Added value: +{
+  "default": [
+    "web"
+  ],
+  "enum": [
+    [
+      "web"
+    ]
+  ],
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 1,
+  "minItems": 1,
+  "type": "array"
+}
  3. Changed7 schema fields changed
    • removedInput schema / properties / enterprise
      Removed value: -{
-  "default": false,
-  "enum": [
-    false
-  ],
-  "type": "boolean"
-}
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of results to return."
    • addedInput schema / properties / query / description
      Added value: +"The search query. Must be non-empty and at most 500 characters."
    • addedInput schema / properties / query / example
      Added value: +"firecrawl web scraping api"
    • changedInput schema / properties / query / maxLength
      Previous value: -2000New value: +500
    • removedInput schema / properties / query / minLength
      Removed value: -1
    • removedInput schema / properties / sources
      Removed value: -{
-  "default": [
-    "web"
-  ],
-  "enum": [
-    [
-      "web"
-    ]
-  ],
-  "items": {
-    "type": "string"
-  },
-  "maxItems": 1,
-  "minItems": 1,
-  "type": "array"
-}
  4. Changed7 schema fields changed
    • addedInput schema / properties / enterprise
      Added value: +{
+  "default": false,
+  "enum": [
+    false
+  ],
+  "type": "boolean"
+}
    • removedInput schema / properties / limit / description
      Removed value: -"Maximum number of results to return."
    • removedInput schema / properties / query / description
      Removed value: -"The search query. Must be non-empty and at most 500 characters."
    • removedInput schema / properties / query / example
      Removed value: -"firecrawl web scraping api"
    • changedInput schema / properties / query / maxLength
      Previous value: -500New value: +2000
    • addedInput schema / properties / query / minLength
      Added value: +1
    • addedInput schema / properties / sources
      Added value: +{
+  "default": [
+    "web"
+  ],
+  "enum": [
+    [
+      "web"
+    ]
+  ],
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 1,
+  "minItems": 1,
+  "type": "array"
+}
  5. First observed

TDQS

D1.3/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is externally supplied. The description adds only pricing-per-call context, which is useful operational context but does not explain what 'destructive' means for a search or describe authentication, rate limits, or result behavior.

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 it is front-loaded with billing boilerplate rather than the tool's purpose. None of its sentences help an agent decide to select or correctly invoke this tool.

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 search tool with a nested request body, several sibling alternatives, and an output schema, the description omits purpose, usage, and parameter semantics entirely. It is not remotely complete enough to guide correct invocation.

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 schema has 0% description coverage and a nested body object, but the description provides no parameter meaning at all. Neither the required query field nor the limit, sources, or enterprise options are explained.

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/pricing boilerplate, leaving the agent to infer 'search' from the name and title alone. Sibling tools include many competing search endpoints, so no differentiation is provided.

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 guidance on when to use this search tool versus alternatives such as post_exa_search, post_tavily_search, or post_perplexity_sonar. No prerequisites, query constraints, or exclusion conditions are mentioned.

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 toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources