Skip to main content
Glama

срезAI — MCP-сервер и поисковый API для ИИ-агентов

Извлечь данные по схеме / Extract data by schema

extract
Read-onlyIdempotent

Читает страницу и возвращает JSON строго по вашей схеме: только запрошенные поля, без текста страницы. Чего на странице нет - приходит null, значения не домысливаются.

Когда: нужны 2-5 конкретных значений - цена, характеристики, автор и дата, список вакансий. Экономит контекст: вместо всей страницы придут только поля. Когда не: нужен связный текст или вы не знаете заранее, что искать, - read_url (и в 4 раза дешевле). Схема: принимается и сокращённая форма - {"title":"string","price":"number?"}, где «?» делает поле необязательным, а «[]» - массивом; полный JSON Schema тоже работает. Описания полей заметно повышают точность разбора. Возвращает: объект по схеме на каждую ссылку. Можно передать до 10 ссылок разом (на бесплатном тарифе до 5) - одна схема применится ко всем. Цена: 2 кредита за каждую ссылку (чтение плюс разбор моделью).

Reads a page and returns JSON strictly following your schema: only the requested fields, no page text. Anything absent from the page comes back as null - values are never invented.

Use when: you need a handful of specific values - price, specs, author and date, a list of job openings. It saves context: you get the fields, not the page. Do not use when: you need prose, or you do not know in advance what to look for - read_url (and 4× cheaper). Schema: a shorthand form is accepted - {"title":"string","price":"number?"}, where "?" marks a field optional and "[]" an array; full JSON Schema works too. Field descriptions noticeably improve extraction accuracy. Returns: one object per link, shaped by your schema. Up to 10 links per call (5 on the free tier), one schema applied to all. Cost: 2 credits per link (page read plus model parsing).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL страницы (http/https) / Page URL (http/https)
urlsNoСписок URL (1-10) вместо url - одна схема на все страницы. Лишнее отбрасывается по тарифу: на бесплатном берём 5, на платном больше. Каждая страница тарифицируется отдельно. / A list of URLs (1-10) instead of url - one schema for all pages; the rest is cut by plan (5 on the free tier). Each page is billed separately.
engineNoКак забирать страницу: auto (по умолчанию), fast, dynamic, stealth. / How to fetch the page: auto (default), fast, dynamic, stealth.
schemaNoСхема результата. Проще всего - сокращённая форма: {"title":"string","price":"number?","tags":"string[]"}, где «?» помечает поле необязательным, а «[]» - массивом. Полный JSON Schema тоже принимается: {"type":"object","properties":{"price":{"type":"number","description":"цена в рублях"}},"required":["price"]}. Типы: string, number, integer, boolean, array, object. Описания полей заметно повышают точность. / The result schema. The simplest form is shorthand: {"title":"string","price":"number?","tags":"string[]"}, where «?» marks the field optional and «[]» marks an array. Full JSON Schema is accepted too. Types: string, number, integer, boolean, array, object. Field descriptions noticeably improve accuracy.
instructionNoУточнение для разбора, если из схемы неочевидно: «бери цену со скидкой», «только вакансии удалённо». / A parsing hint when the schema alone is ambiguous: «use the discounted price», «remote positions only».

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / urls / description
      Previous value: -"Список URL (1-5) вместо url - одна схема на все страницы. Каждая страница тарифицируется отдельно. / A list of URLs (1-5) instead of url - one schema for all pages. Each page is billed separately."New value: +"Список URL (1-10) вместо url - одна схема на все страницы. Лишнее отбрасывается по тарифу: на бесплатном берём 5, на платном больше. Каждая страница тарифицируется отдельно. / A list of URLs (1-10) instead of url - one schema for all pages; the rest is cut by plan (5 on the free tier). Each page is billed separately."
    • changedInput schema / properties / urls / maxItems
      Previous value: -5New value: +10
  2. Changed2 schema fields changed
    • changedInput schema / properties / schema / description
      Previous value: -"Схема результата. Проще всего — сокращённая форма: {\"title\":\"string\",\"price\":\"number?\",\"tags\":\"string[]\"}, где «?» помечает поле необязательным, а «[]» — массивом. Полный JSON Schema тоже принимается: {\"type\":\"object\",\"properties\":{\"price\":{\"type\":\"number\",\"description\":\"цена в рублях\"}},\"required\":[\"price\"]}. Типы: string, number, integer, boolean, array, object. Описания полей заметно повышают точность. / The result schema. The simplest form is shorthand: {\"title\":\"string\",\"price\":\"number?\",\"tags\":\"string[]\"}, where «?» marks the field optional and «[]» marks an array. Full JSON Schema is accepted too. Types: string, number, integer, boolean, array, object. Field descriptions noticeably improve accuracy."New value: +"Схема результата. Проще всего - сокращённая форма: {\"title\":\"string\",\"price\":\"number?\",\"tags\":\"string[]\"}, где «?» помечает поле необязательным, а «[]» - массивом. Полный JSON Schema тоже принимается: {\"type\":\"object\",\"properties\":{\"price\":{\"type\":\"number\",\"description\":\"цена в рублях\"}},\"required\":[\"price\"]}. Типы: string, number, integer, boolean, array, object. Описания полей заметно повышают точность. / The result schema. The simplest form is shorthand: {\"title\":\"string\",\"price\":\"number?\",\"tags\":\"string[]\"}, where «?» marks the field optional and «[]» marks an array. Full JSON Schema is accepted too. Types: string, number, integer, boolean, array, object. Field descriptions noticeably improve accuracy."
    • changedInput schema / properties / urls / description
      Previous value: -"Список URL (1–5) вместо url — одна схема на все страницы. Каждая страница тарифицируется отдельно. / A list of URLs (1–5) instead of url — one schema for all pages. Each page is billed separately."New value: +"Список URL (1-5) вместо url - одна схема на все страницы. Каждая страница тарифицируется отдельно. / A list of URLs (1-5) instead of url - one schema for all pages. Each page is billed separately."
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, openWorld, non-destructive), and the description goes further with genuinely non-derivable behavior: absent fields return null rather than being invented, batching limits (10 links, 5 on free tier), and per-link billing of 2 credits. That is exactly the added context annotations cannot provide.

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?

Every block (purpose, when/when-not, schema, returns, cost) is front-loaded and earns its place, with no filler. The one cost is full bilingual duplication, which roughly doubles the text for the same information.

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?

With no output schema, the description carries the return-value burden and does so ('one object per link, shaped by your schema'). Combined with the schema-grammar guidance, null semantics, batching cap and billing, an agent has everything needed to call this correctly.

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 100%, so the baseline is 3; the description earns an extra point by explaining the shorthand schema grammar ('?' for optional, '[]' for array), confirming full JSON Schema is accepted, and noting that field descriptions improve extraction accuracy, plus how `instruction` resolves schema ambiguity. It does duplicate some of what the schema already states, which keeps it from a 5.

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 verb+resource pair: it reads a page and returns JSON constrained to the caller's schema, explicitly excluding page text. It also names the sibling it is not (read_url) and the trade-off between them, so an agent can distinguish it from fetch_page/read_url/crawl without opening a schema.

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 an explicit "Use when" (2-5 concrete values: price, specs, author/date, job listings) and an explicit "Do not use when" (prose needed, or you don't know what to look for) with the alternative read_url named and a cost ratio given. Nothing is left to inference.

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.