Skip to main content
Glama

Find where a photo or video was taken

locate_media

Estimate where a photo or 1–4 video frames were filmed, returning place name, country, coordinates, confidence, uncertainty radius in km, visual clues and alternatives. Uses 1 check when a location is found; 0 checks if unknown or failed.

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": "locate_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
hintNoOptional context hint, e.g. "filmed in summer 2019".
kindNoOptional media type hint (photo or video).
takenNoOptional recording date (YYYY-MM-DD) from EXIF or video metadata.
image_urlNoPublic https URL of a single JPEG, PNG or WebP image (up to 5 MB).
image_urlsNoUp to 4 public https URLs of evenly spaced frames from one video.
image_base64NoBase64-encoded JPEG, PNG or WebP image (with or without data: prefix).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already disclose openWorldHint=true, non-read-only and non-idempotent behavior, but the description adds the key thing they cannot convey: the credit-charging rule, including conditional free calls on unknown or failed lookups. It stops short of describing input eligibility rules or failure modes beyond that, so it earns a 4 rather than a 5.

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 sentences, both front-loaded with the core capability and the billing rule, with zero filler. Every clause carries information the agent needs.

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?

With no output schema, the description correctly spends its words enumerating the returned fields. However, for a tool with zero required parameters and three mutually overlapping media inputs (image_url, image_urls, image_base64), it never states that exactly one must be supplied, leaving a real ambiguity about how to construct a valid call.

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 100% with per-parameter descriptions for hint, kind, taken, image_url, image_urls and image_base64, so the schema carries the parameter burden. The description adds only the frame-count semantics (1–4 frames from one video) that maps image_url against image_urls, which is modest added value.

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 description names a specific action (estimate where a photo or 1–4 video frames were filmed) and enumerates what comes back (place name, country, coordinates, confidence, uncertainty radius, visual clues, alternatives), so an agent knows exactly the capability. It does not distinguish itself from siblings such as detect_ai_media, which is the only missing element for a 5.

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?

Usage is only implied by the input shape: you have a photo or up to four evenly spaced frames from one video and want a location estimate. The cost note (1 check on success, 0 on unknown/failure) helps an agent decide whether to call, but there is no explicit when-not-to-use guidance and no named alternative.

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