Skip to main content
Glama

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

by ru.srezai
OverviewDiscussionsAdmin

Поиск изображений / Image search

image_search
Read-only

Ищет изображения по текстовому запросу и возвращает прямые ссылки на файлы, страницу-источник и разрешение.

Когда: нужны картинки, фотографии, логотипы, схемы. Когда не: нужен текст или факты - web_search; нужно увидеть, как выглядит конкретная страница, - fetch_page. Возвращает: только ссылки и метаданные - файлы не скачиваются и в ответе не появляются. Ставьте num: 1-3, если картинка нужна одна: по умолчанию 12, максимум 48, и полный список занимает десятки килобайт контекста. Цена: 1 кредит за вызов, независимо от num.

Searches for images by a text query and returns direct file links, the source page and resolution.

Use when: you need pictures, photos, logos or diagrams. Do not use when: you need text or facts - web_search; you need to see what a specific page looks like - fetch_page. Returns: links and metadata only - files are never downloaded or embedded in the response. Pass num: 1-3 when you need a single image: the default is 12, the maximum 48, and a full list costs tens of kilobytes of context. Cost: 1 credit per call regardless of num.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numNoСколько картинок вернуть (1-48, по умолчанию 12). Нужна одна картинка - просите 1-3, не тратьте контекст. / How many images to return (1-48, default 12). Need just one - ask for 1-3 and save context.
safeNoБезопасный поиск / Safe search (on by default)
queryYesЧто искать / What to search for
timeRangeNoСвежесть / Recency: all, day, week, month, year

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / num / description
      Previous value: -"Сколько картинок вернуть (1–48, по умолчанию 12). Нужна одна картинка — просите 1–3, не тратьте контекст. / How many images to return (1–48, default 12). Need just one — ask for 1–3 and save context."New value: +"Сколько картинок вернуть (1-48, по умолчанию 12). Нужна одна картинка - просите 1-3, не тратьте контекст. / How many images to return (1-48, default 12). Need just one - ask for 1-3 and save context."
  2. Changed1 schema field changed
    • changedInput schema / properties / timeRange / description
      Previous value: -"Свежесть / Recency: '', day, week, month, year"New value: +"Свежесть / Recency: all, day, week, month, year"
  3. Changed1 schema field changed
    • changedInput schema / properties / timeRange / enum
      Previous value: -[
-  "",
-  "day",
-  "week",
-  "month",
-  "year"
-]New value: +[
+  "all",
+  "day",
+  "week",
+  "month",
+  "year"
+]
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses that files are never downloaded or embedded, that the default is 12 results and the max 48, that a full list costs tens of kilobytes of context, and that each call costs 1 credit regardless of num. This is exactly the cost/behavioral context annotations cannot express.

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?

Each language version is tightly structured and front-loaded (purpose, when/when-not, returns, cost). However, the full description is duplicated verbatim in Russian and English, which doubles the token cost for no informational gain.

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?

Without an output schema, the description still explains the return payload (direct file links, source page, resolution) and what is deliberately absent (the files themselves). Combined with cost, default, and cap disclosures, 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.

Parameters3/5

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

Schema description coverage is 100%, so all four parameters are already documented in the schema, including the num 1-3 guidance for single-image requests. The description restates the num advice but adds nothing new about query, safe, or timeRange, so the baseline 3 applies.

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?

States a specific verb and resource ("searches for images by a text query") and explicitly names the two siblings that cover adjacent needs (web_search for text/facts, fetch_page for page rendering). An agent can distinguish this from all 11 siblings without opening any 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?

Explicit "When:" / "When not:" structure with concrete triggers (pictures, photos, logos, diagrams) and named alternatives for each non-trigger case. 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.

All срезAI — MCP-сервер и поисковый API для ИИ-агентов toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources