Skip to main content
Glama
Sign In
Copyseeker MCP Server

Copyseeker MCP Server

Official
by copyseeker-net
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Reverse image search

reverse_image_search
Read-only

Find web pages that display a given image and the copies each page uses, ranked by prominence, to trace an image's origin, first publisher, or unauthorized reuse.

Instructions

Find the web pages that show this image, with the copies of it each page uses, ranked by how prominent the page is. Use it to find where an image came from, who published it first, or where it is reused without permission. Costs 1 credit.

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": {
      "image": "<image>"
    },
    "name": "reverse_image_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYesDirect URL of the image file (http or https, not the web page showing it), or the absolute path to a local image file up to 20 MB.
max_resultsNoMost pages to return, best ranked first.

Output Schema

NameRequiredDescriptionDefault
pagesYes
totalPagesYesPages Copyseeker found, before max_results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, open-world, non-destructive, and non-idempotent behavior, so the description's main addition is the 1-credit cost and the ranked per-page copy output. It does not discuss authentication, rate limits, or failure cases, but those are less critical given the rich annotations and output schema.

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?

Two tightly written sentences front-load the core action and result shape, then add use cases and cost. Every sentence contributes information without repetition or filler.

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?

The description is complete for this tool: annotations cover the safety and open-world profile, schema coverage is full, and an output schema exists for return values. The important operational fact, a 1-credit cost, is explicitly stated.

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 100%, so both the image input and max_results are already fully documented in structured fields. The description adds no parameter-level detail such as URL formatting or result-size tradeoffs beyond what the schema provides, making the baseline 3 appropriate.

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?

Uses a specific verb and resource: finding web pages that show a given image, including per-page copies ranked by prominence. This clearly separates it from image detection siblings, though it never names or explicitly contrasts those alternatives.

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

Usage Guidelines4/5

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

Gives clear when-to-use guidance with three concrete scenarios: tracing an image's origin, identifying the first publisher, and finding unauthorized reuse. It does not state exclusions or explicitly route to the sibling detection tools, so it stops short of full alternative guidance.

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