Skip to main content
Glama

срезAI — Search API for AI agents

by ru.srezai
OverviewAdmin

Поиск изображений / 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. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / timeRange / description
      Previous value: -"Свежесть / Recency: '', day, week, month, year"New value: +"Свежесть / Recency: all, day, week, month, year"
  2. Changed1 schema field changed
    • changedInput schema / properties / timeRange / enum
      Previous value: -[
-  "",
-  "day",
-  "week",
-  "month",
-  "year"
-]New value: +[
+  "all",
+  "day",
+  "week",
+  "month",
+  "year"
+]
  3. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: it states that files are never downloaded or embedded, and it discloses the cost (1 credit per call) and the context-size impact of large num values. This goes beyond the annotations, though it doesn't detail response structure or pagination, which is minor given the annotations.

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 well-structured with clear sections (When, When not, Returns, Cost) and is front-loaded with the core purpose. Every sentence serves a purpose, and the bilingual format is consistent. It's concise yet comprehensive, with no fluff.

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 read-only search tool with full schema coverage and no output schema, the description covers all essential aspects: purpose, usage conditions, behavioral constraints, cost, and parameter guidance. The agent has everything needed to call the tool correctly and interpret results, given the annotations cover safety.

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 100%, so the schema already documents all parameters. The description adds value by explaining the practical implications of num (context cost) and reinforcing the default and maximum, which helps the agent make better parameter choices. It doesn't add new syntax details but enhances the semantic understanding of num's impact.

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 clearly states the tool's function: searching for images by text query and returning direct file links, source page, and resolution. It explicitly distinguishes itself from siblings like web_search and fetch_page, making its purpose unambiguous.

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 provides explicit when-to-use and when-not-to-use guidance, naming alternatives (web_search for text/facts, fetch_page for page appearance). It also gives practical usage tips like setting num to 1-3 for a single image, which is actionable and clear.

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

All срезAI — Search API for AI agents toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources