Skip to main content
Glama
aidvizhhub

camoufox-research

by aidvizhhub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

extract

Извлечение по схеме (Firecrawl extract): schema — JSON {"поле": "css:.price"} или {"поле": {"selector": ".price", "attr": "text|href|src"}}. Селекторы: CSS ("css:", ".price"), XPath ("//div[@class='x']" или "xpath=..."). Возвращает JSON.

Instructions

Извлечение по схеме (Firecrawl extract): schema — JSON {"поле": "css:.price"} или {"поле": {"selector": ".price", "attr": "text|href|src"}}. Селекторы: CSS ("css:", ".price"), XPath ("//div[@class='x']" или "xpath=..."). Возвращает JSON. llm=True — извлечение ИЗ ТЕКСТА страницы (LLM): schema — {"поле": подсказка} или {"поле": {"hint": "..."}}; работает, где селекторы хрупкие; требует LLM (DeepSeek/Ollama), иначе честный ответ «недоступен». КОГДА: нужны КОНКРЕТНЫЕ поля при СТАБИЛЬНОЙ структуре (CSS/XPath); структура неизвестна/меняется → llm=True. НЕ КОГДА: нужен сплошной текст → fetch_page / batch_fetch; нужны таблицы → table_extract; не знаешь селектор → snapshot сначала (найти элементы с ref).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
llmNo
urlYes
schemaYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.18.1
    • addedInput schema / properties / llm
      Added value: +{
+  "default": false,
+  "title": "Llm",
+  "type": "boolean"
+}
  2. Addedv0.2.0

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral disclosure burden. It explains the return type (JSON), the two extraction modes, the LLM dependency for llm=True, and the honest 'unavailable' failure response. It also clarifies that llm=True extracts from page text rather than the DOM.

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?

The description is dense but well-structured, using WHEN and NOT WHEN headers to organize usage guidance. Every sentence adds operational value: schema formats, selector syntax, mode differences, and exclusions. No filler or redundant restatement of the tool name.

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

Completeness5/5

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

For a tool with three parameters and no annotations, the description covers all necessary context: schema syntax, selector languages, llm behavior, failure mode, and routing to alternatives. An output schema exists, so detailed return-shape documentation is not required from the description.

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

Parameters5/5

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

Schema description coverage is 0%, but the description fully compensates. It documents the schema parameter with concrete JSON examples for CSS, XPath, attributes, and hints; it explains the llm boolean's meaning and default behavior. The url parameter remains self-evident from the tool's purpose.

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 states a specific operation: schema-based extraction from a URL, returning JSON. It clearly distinguishes itself from sibling tools by naming fetch_page, batch_fetch, table_extract, and snapshot in its NOT WHEN guidance. The two modes (selector-based and llm=True) are explicit.

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?

The description includes explicit WHEN and NOT WHEN sections. It tells the agent to use llm=True when the page structure is unknown or unstable, and to use alternatives for full text, tables, or when a selector is unknown. This is strong routing guidance relative to sibling tools.

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

Deploy Server

Other Tools