Skip to main content
Glama

case_image_reverse

Find pages using an image through TinEye, with manual search links returned when no API key is configured.

Instructions

Find pages using an image through TinEye API, plus manual search links.

TinEye needs a paid TINEYE_API_KEY. If the image is local, invoking this tool with a key and use_tineye=True uploads it to TinEye. With no key it returns manual search pages, but no claimed matches. A matching page is not proof that its account owns or depicts the image's labeled person.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "case": "<case>",
      "image_id": "<image_id>"
    },
    "name": "case_image_reverse"
  }
}

Input Schema

NameRequiredDescriptionDefault
caseYes
limitNo
image_idYes
use_tineyeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does substantial work: it discloses the paid API key requirement, that a local image is uploaded to a third party, the degraded no-key behavior, and an important epistemic caveat that a matching page is not proof of ownership or identity. It omits rate limits, pagination, and what a successful response contains.

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?

Four short sentences, front-loaded with the core purpose, then the key/upload behavior, then the caveat. Little waste, though the caveat sentence is slightly dense and could be split.

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?

There is no output schema and no parameter documentation, so the description must cover a lot; it handles auth, privacy, and fallback behavior but leaves the case scoping, result limit, and return shape unexplained. Adequate for gating a call, incomplete for predicting results.

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 coverage is 0%, so the description must compensate and only partly does: it explains use_tineye's effect and implies what the image reference means. The required 'case' parameter and the 'limit' parameter are never mentioned, leaving half the inputs undocumented anywhere.

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 first sentence gives a specific verb and resource ('Find pages using an image') and names the mechanism (TinEye API plus manual search links). It is clearly a reverse-image lookup rather than a similarity or crop tool, though it does not explicitly contrast itself with sibling case_image_similar.

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?

It explains the conditional operating modes well: with a paid TINEYE_API_KEY and use_tineye=True a local image is uploaded, and with no key the tool degrades to manual search links. It stops short of saying when to prefer this over case_image_similar or image_analyze, so the agent must infer the alternative.

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