Skip to main content
Glama
Octen-Team

octen-mcp

Official
by Octen-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Image Search

image_search
Read-only

Find images by text or reference image, returning ranked results with titles, sources, and thumbnails. Use for pictures, diagrams, screenshots, or UI design 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.6/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so safety is covered. The description adds genuinely useful non-annotation context: Beta access gating, the strict mutual-exclusivity rule across query/image_url/image_data, and the fact that `topic=design` returns a structured `summary` and `html_snippet`.

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?

Front-loaded with the core action and the mode-selection rule before the design-topic detail. Slightly padded: 'Never more than one' repeats the same constraint stated immediately before, and the trailing keyword list is redundant with the body.

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 10-param, 0-required tool with no output schema, the description covers return shape, access gating, the mode mutual-exclusion rule, and the design-mode special output — everything an agent needs to invoke it 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 baseline is 3; the description nonetheless adds real semantics beyond the schema — the exact-one-of constraint on the three input modes and the behavioral effect of `topic=design` on the result payload, neither of which is fully conveyed by the schema text alone.

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 (find images on the web) with two distinct modes (text query or reference image) and enumerates the returned fields. It also carves out the boundary against sibling `search` by saying 'not for general text web search'.

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?

Gives explicit when-to-use ('user wants pictures, photos, diagrams, screenshots, or visual references') and when-not ('not for general text web search'), plus a routing rule for `topic=design`. An agent can select between this, `search`, `news_search`, and `video_search` without ambiguity.

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