Firecrawl by Nova (CIVAI)

firecrawl_find_tools

Browse Alexandria data providers and workflows or read a selected contract. Alexandria covers companies, people, jobs, finance and filings, public records and government spending, real estate, places and restaurants, retail and prices, package registries and developer data, news, research, and more: typed, sourced records through published contracts. Prefer normal firecrawl_search for a data task; it already returns matching providers. Use this tool when the contract you need was not returned in full, to browse a category when search found nothing, or before scraping the same fields from several pages. Discovery is free. Use query for semantic discovery or urls to find providers for a website. With no arguments, browse categories, then providers and tools. Contracts describe the inputs and outputs for execution through firecrawl_scrape. nextTool identifies further discovery or pagination. Discovery does not execute providers. Use firecrawl_search when you also need web results.

Input Schema

Name	Required	Description
`urls`	No
`level`	No	Usually omit: it follows the arguments (tools for query, urls, providers, capabilities or groups; providers for categories; categories with none). Set providers or groups to list those within a category or url scope instead of tools. query, or a non-empty expand with any other argument, returns tools.
`limit`	No
`query`	No	Semantic lookup of tools for the data you need. Selectors constrain the search.
`expand`	No	Use ["options", "response"] for inputs and output shape without example payloads; [] keeps results compact. Omit for full contracts on selected capabilities.
`groups`	No	Optional group IDs for explicit group browsing.
`offset`	No
`objective`	Yes	The user's underlying goal for this call, in one sentence: what they are ultimately trying to accomplish, not a restatement of the URL or query. Reuse it across related calls. Avoid sensitive information.
`providers`	No	Values from each listed tool's `provider` field (e.g. "apps-apple-com"). Alone, lists that provider's compact tools; with capabilities, scopes them.
`categories`	No	Category IDs returned by an empty call. Lists providers by default.
`capabilities`	No	Values from each listed tool's `capability` field (e.g. "apps/app"). Put the provider in `providers`: {"providers": ["apps-apple-com"], "capabilities": ["apps/app"]}. A selected capability expands its complete contract by default.
`includeCosts`	No	Include per-capability credit prices (creditsCost, perRecord) in tool results.
`conversationId`	No	conversationId 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.

First observedNov 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and discloses key traits: discovery is free, discovery does not execute providers, contracts describe inputs/outputs for execution through firecrawl_scrape, and nextTool signals further discovery or pagination. It stops short of describing result sizes, rate limits, or the pagination mechanics behind offset/limit.

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?

Purpose is front-loaded and every sentence carries routing or behavioral information. There is mild redundancy in restating the discovery/free and non-execution points separately, but nothing that materially wastes space.

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 13-parameter discovery tool with no annotations and no output schema, the description covers the core workflow, the contract-to-scrape handoff, and the nextTool continuation signal. Pagination parameters and cost inclusion are left entirely to the schema, which leaves a small gap in the overall picture.

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 77%, so the baseline is 3; the description adds practical semantics by pairing query with semantic discovery, urls with finding providers for a website, and describing the no-argument browse flow (categories, then providers and tools). It does not add meaning for offset, limit, includeCosts, or level beyond what the schema already documents.

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

Purpose5/5

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

The description names a specific verb and resource set: browsing Alexandria providers/workflows and reading selected contracts, with a concrete domain list (companies, people, finance, public records, real estate, etc.). It explicitly contrasts itself with firecrawl_search and firecrawl_scrape, so an agent can distinguish it from siblings without opening schemas.

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

Usage Guidelines5/5

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

It gives explicit when-not ('Prefer normal firecrawl_search for a data task; it already returns matching providers') and three concrete when-to conditions (contract not returned in full, browse a category after empty search, before scraping the same fields across pages). It closes by routing to firecrawl_search when web results are also needed.

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

All Firecrawl by Nova (CIVAI) 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?