Skip to main content
Glama

Firecrawl by Nova (CIVAI)

firecrawl_feedback

Firecrawl uses this feedback to find and fix results that were wrong, missing or unhelpful, which improves the data later calls return.

Submit concise quality feedback for a completed search, scrape, parse, or map job. Provide the endpoint, job ID, rating, and relevant issue codes or small contextual fields; omit large page contents and raw outputs.

For an Alexandria session, set endpoint to alexandria, omit jobId, and provide requestedWebsite (url and requestedFunctionality), objective, rationale, and rating. objective is the underlying goal behind the session: what you or your user were ultimately trying to accomplish (for example, "shortlist federal IT contracts to bid on this quarter"), not only what was needed from this website. Optional providerFeedback and capabilityFeedback describe gaps or errors. Capability issues: new_capability_request (requires requestedFunctionality), missing_capability, insufficient_functionality, incorrect_result, execution_error, other. Alexandria results carry a feedbackRef per call. The overall rating covers every call in this session; callRatings [{ref, rating}] rate individual calls by feedbackRef. Alexandria feedback must arrive within 20 minutes of the team's latest Alexandria search, discovery, or execution; later feedback is rejected. Eligible feedback can refund 1 credit; refunds are subject to daily caps per website and per team.

Returns submission status, feedback ID, and accounting fields.

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": {
      "endpoint": "<endpoint>",
      "rating": "<rating>"
    },
    "name": "firecrawl_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
noteNo
tagsNo
jobIdNo
issuesNo
ratingYes
endpointYes
metadataNo
objectiveNoThe user's underlying goal in one sentence, not a restatement of this call's arguments. Reuse it across related calls. Firecrawl uses it to learn what agents need and improve its results. No personal data, secrets or the user's exact words.
rationaleNo
callRatingsNo
pageNumbersNo
conversationIdNoconversationId 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.
missingContentNo
valuableSourcesNo
providerFeedbackNo
querySuggestionsNo
requestedWebsiteNo
capabilityFeedbackNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / objective / description
      Added value: +"The user's underlying goal in one sentence, not a restatement of this call's arguments. Reuse it across related calls. Firecrawl uses it to learn what agents need and improve its results. No personal data, secrets or the user's exact words."
  2. Changed1 schema field changed
    • addedInput schema / properties / callRatings
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "rating": {
      +        "enum": [
      +          "good",
      +          "partial",
      +          "bad"
      +        ],
      +        "type": "string"
      +      },
      +      "ref": {
      +        "maxLength": 32,
      +        "minLength": 1,
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "ref",
      +      "rating"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / metadata / additionalProperties
      Previous value: -{}New value: +true
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses the 20-minute submission window for Alexandria feedback, that late feedback is rejected, the 1-credit refund and daily caps, and the returned fields (status, feedback ID, accounting). It omits detail on failure modes or partial acceptance, keeping it below a 5.

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?

It is front-loaded with purpose and impact, then layers conditional and error-specific guidance densely. Length is justified by 19 parameters, but the objective explanation partially duplicates the schema's own objective description, costing a little efficiency.

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 complex 19-parameter, nested-object feedback tool with no output schema and no annotations, the description covers the critical branching logic, timing constraints, and refund behavior an agent needs to call it correctly. It leaves a handful of auxiliary parameters unexplained, but the core invocation path is complete.

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 description coverage is only 11%, so the description must compensate, and it does for several influential params: endpoint values, jobId omission for Alexandria, requestedWebsite shape, objective semantics, callRatings ref/rating mapping to feedbackRef, and the full capability issue enum. Many params (note, tags, issues, metadata, pageNumbers, missingContent, valuableSources, querySuggestions) still receive no explanation beyond their schema types.

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 opening sentence gives a specific verb and resource: submitting quality feedback for a completed search, scrape, parse, or map job, and describes the downstream effect. It does not, however, distinguish itself from the sibling firecrawl_search_feedback, which an agent could conflate given the overlapping 'search' endpoint.

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

Usage Guidelines4/5

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

It provides clear conditional guidance (for Alexandria sessions set endpoint to alexandria, omit jobId, supply requestedWebsite/objective/rationale) and tells the agent to omit large page contents and raw outputs. It stops short of naming when to use a different feedback tool or explicitly excluding cases.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources