Skip to main content
Glama
Octen-Team

octen-mcp

Official
by Octen-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

image_search

Read-only

Find web images by text query or reference image, returning ranked results with titles, sources, dimensions, and descriptions. Use for photos, diagrams, screenshots, or visual references.

Instructions

Find images on the web by text query OR by a reference image — returns ranked results (title, source page, dimensions, thumbnail, description, summary). In Beta; contact us to request beta access. Pass exactly one of: a text query, an image_url (a picture already on the web), or image_data (base64, for a picture you hold). Never more than one. Set topic to design for UI design references — each result then carries a structured style summary and an html_snippet for building/restyling frontends. Use this when the user wants pictures, photos, diagrams, screenshots, or visual references — not for general text web search.

keywords: find images, image search, photos, pictures, screenshots, visual reference, diagram, icon, illustration, UI design, reference image

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of results to return (1-10). Default 5.
queryNoText query describing the images to find. Exactly one of `query`, `image_url` or `image_data` — never more than one.
topicNoImage category: `general` for broad image search, `design` for design / illustration oriented results. Default general.general
timeoutNoRequest timeout in seconds (1-60). Defaults to 30s if unset.
image_urlNoPublic image URL to search by visual similarity. Exactly one of `query`, `image_url` or `image_data` — never more than one.
image_dataNoBase64-encoded image to search by visual similarity, for an image you hold rather than one already on the web. At most 5MB encoded; JPEG, PNG, WEBP, BMP, TIFF, ICO, DIB, ICNS or SGI. A `data:` URI is accepted — its payload is used. Exactly one of `query`, `image_url` or `image_data` — never more than one.
safesearchNoAdult-content filter. Default strict.strict
html_snippetNoReturn an HTML snippet of the source context per result. Omit to use the server default.
exclude_domainsNoDrop results from these domains.
include_domainsNoOnly return results from these domains (e.g. 'unsplash.com').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.5.0
    • removedInput schema / properties / end_time
      Removed value: -{
-  "description": "Upper bound for the time window, ISO 8601.",
-  "type": "string"
-}
    • changedInput schema / properties / html_snippet / properties / max_tokens / description
      Previous value: -"Max tokens per HTML snippet (min 100). Default 5000."New value: +"Max tokens per HTML snippet (100-100000). Default 5000."
    • addedInput schema / properties / html_snippet / properties / max_tokens / maximum
      Added value: +100000
    • addedInput schema / properties / image_data
      Added value: +{
+  "description": "Base64-encoded image to search by visual similarity, for an image you hold rather than one already on the web. At most 5MB encoded; JPEG, PNG, WEBP, BMP, TIFF, ICO, DIB, ICNS or SGI. A `data:` URI is accepted — its payload is used. Exactly one of `query`, `image_url` or `image_data` — never more than one.",
+  "maxLength": 5242880,
+  "type": "string"
+}
    • changedInput schema / properties / image_url / description
      Previous value: -"Optional public image URL to search by reference image (visual similarity), in addition to the text `query`."New value: +"Public image URL to search by visual similarity. Exactly one of `query`, `image_url` or `image_data` — never more than one."
    • changedInput schema / properties / query / description
      Previous value: -"Text query describing the images to find."New value: +"Text query describing the images to find. Exactly one of `query`, `image_url` or `image_data` — never more than one."
    • removedInput schema / properties / start_time
      Removed value: -{
-  "description": "Lower bound for the time window, ISO 8601 (e.g. '2025-01-01T00:00:00Z').",
-  "type": "string"
-}
    • removedInput schema / properties / time_range
      Removed value: -{
-  "description": "Relative time window (e.g. `week`, `month`). Mutually exclusive with `start_time`/`end_time` — if both are given, the absolute range wins.",
-  "enum": [
-    "day",
-    "week",
-    "month",
-    "year",
-    "d",
-    "w",
-    "m",
-    "y"
-  ],
-  "type": "string"
-}
    • removedInput schema / required
      Removed value: -[
-  "query"
-]
  2. Changed1 schema field changedv0.4.2
    • changedInput schema / properties / timeout / description
      Previous value: -"Request timeout in seconds (1-60)."New value: +"Request timeout in seconds (1-60). Defaults to 30s if unset."
  3. Addedv0.3.1

TDQS

A4.8/5.0
Behavior5/5

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

The description goes well beyond annotations by disclosing that the tool is in Beta and requires access, that results are ranked, and what fields are returned. It also clarifies the design-topic behavior (structured style summary and html_snippet) and the accepted image formats and size limit, giving the agent a realistic operational picture.

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?

The description is dense and well front-loaded, with the core function, key constraints, and usage guidance near the top. The trailing keyword list is somewhat redundant with the prose, but for a tool with 10 parameters and multiple modes, the length is justified and each section earns its place.

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?

There is no output schema, but the description compensates by enumerating the returned fields: title, source page, dimensions, thumbnail, description, summary, and html_snippet in design mode. It also covers access requirements, input modes, and the suggestion to use it for visual references, making the tool callable end-to-end without missing critical context.

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 adds meaning on top of the schema by explaining the `topic=design` effect on result structure, the 'pass exactly one' exclusivity rule, and the practical distinction between `image_url` and `image_data`. It does not need to restate every schema detail.

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 opens with a specific verb and resource — 'Find images on the web by text query OR by a reference image' — and lists the returned result fields. It clearly distinguishes image search from general text web search and from the sibling tools by stating exactly what kind of content it retrieves.

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 explicitly states when to use the tool: 'Use this when the user wants pictures, photos, diagrams, screenshots, or visual references — not for general text web search.' It also gives mode-specific guidance for `topic=design`, and explains the mutual-exclusivity rule for `query`, `image_url`, and `image_data` so an agent knows how to choose among them.

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