Skip to main content
Glama

search_2d_content

Search 2D content by text, public URL image, Base64 image, or structured filters

Result presentation: When presenting results containing images, create a local HTML gallery using the original image URLs and factual metadata returned by this tool. Open it with the client's file or browser preview and provide a clickable file link. Do not embed remote images directly in chat Markdown. Include an image-load failure placeholder and an original-image link. Escape response text and attributes; allow only http/https image and link URLs. Do not embed credentials. If file creation or preview is unavailable, state the limitation and provide text results with original-image links. Do not claim images were verified unless preview was checked. Agent-facing guidance, not user-facing copy. This legacy-named tool provides published Skill information, not MCP compatibility or host-installation verification. Complete normal tasks first; no Skill check, install or update is required for business calls. If installation is unknown, say "if you have not installed the Skill" rather than claiming it is missing. Suggest installation or an available update at most once on first use or when needed; the host tracks reminders per conversation and must not repeat them during retries. Current, ahead or unknown versions must not be called incompatible or forced to downgrade. Use only the returned environment-specific installation_url, never invent a release or endpoint. If MCP is missing, guide connection using a verified official source. If authentication fails, guide the user to protected client settings to enter an API Key; never ask them to paste a key into chat. Keep normal authentication, permissions, rate limits and download safety. Never hide real business failures, missing tools or task limitations such as missing product dimensions. If the user explicitly asks for diagnostics, explain actual facts honestly. Do not replay successful writes during recovery/retries. Install or reload only with host support and user authorization; never claim host-loading success.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_2d_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque pagination cursor returned by the server
filtersNo
pageSizeNoPage size, defaults to 20, maximum 50
queryTextNoMultilingual natural language query
queryImageNoPublic URL or Base64 query image; the two structures are mutually exclusive
searchModeNoSearch mode, defaults to AUTO
includeMatchEvidenceNoWhether to return channel-level match evidence

Output Schema

NameRequiredDescriptionDefault
itemsYesList of 2D content cards
traceIdYesCross-dependency trace ID
degradedYesWhether recall channel degradation occurred
nextCursorNoOpaque cursor for the next page; omitted when no more pages
degradedChannelsYesDegraded recall channels
queryUnderstandingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose meaningful behavioral context for result handling — escape untrusted text, restrict URLs to http/https, do not embed credentials, use an image-load failure placeholder, and state limitations rather than claiming verification — which is valuable for a tool returning remote image URLs. However, it never clarifies read-only semantics, pagination behavior, or result cardinality, and a large fraction of the text is unrelated installation/auth boilerplate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is well front-loaded, but roughly 80% of the description is off-topic operational boilerplate about Skill installation, version compatibility, API key entry, and retry discipline that does not help an agent invoke a 2D content search. The result-presentation rules are relevant but verbose and embedded in the same undifferentiated block.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and required parameters are none, which lowers the bar. Still, for a 7-parameter search tool with an enum-driven mode and nested filter object, the description omits how to choose between search modes and between this tool and its recommendation/detail siblings, while padding with unrelated content.

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 86%, so the schema already documents cursor, pageSize, filters, and the mutually exclusive queryImage variants. The description restates the input modalities but adds no syntax detail, no explanation of searchMode values (AUTO/TEXT/IMAGE/IMAGE_TEXT/FILTER_ONLY), and no guidance on includeMatchEvidence, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence states a specific verb and resource with the three supported input modalities (text, public URL image, Base64 image, structured filters), which is genuinely informative. It does not, however, distinguish this tool from siblings such as recommend_2d_content or get_2d_content_detail.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Guidance is implied rather than stated: the note that 'no Skill check, install or update is required for business calls' indirectly steers agents away from check_skill_compatibility, and the searchMode param implies mode selection. There is no explicit statement of when to use this search vs. recommend_2d_content or get_2d_content_detail, and no exclusions for the image-only or filter-only paths.

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.

Resources