Skip to main content
Glama

Bulk IP Geolocation Lookup

ipgeolocation_bulk_lookup
Read-onlyIdempotent

Look up geolocation data for up to 50,000 IP addresses or hostnames in a single request. Returns an array of geolocation objects with individual error handling.

Instructions

Look up geolocation data for up to 50,000 IP addresses or hostnames in one request. Returns an array of geolocation objects — same fields as the single lookup. Individual IP failures include a 'message' field; they don't block other results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipsYesList of IPv4/IPv6 addresses or hostnames to look up (max 50,000). Example: ["8.8.8.8", "1.1.1.1"]
langNoLanguage for location name fields. Defaults to English.en
includeNoAdditional data modules to include. Available: security, hostname, liveHostname, hostnameFallbackLive, user_agent, abuse, dma_code, time_zone, geo_accuracy.
fieldsNoComma-separated dot-path fields to include in the response (allowlist). E.g. 'location.city,asn.organization'.
excludesNoComma-separated dot-path fields to exclude from the response (denylist). E.g. 'location.city,asn.organization'.
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint. The description adds useful behavioral context about partial failures (individual IP failures have a 'message' field and don't block others) and the batch limit.

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 with zero wasted words. Front-loaded with the core purpose and limit, followed by return and error handling details.

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

Completeness4/5

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

Given the rich schema and annotations, the description covers the essential points: bulk vs single, limit, and failure handling. It does not detail return structure, but that is inferred from the single lookup tool.

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 detailed descriptions for each parameter (maxItems, example, enums). The description adds minimal parameter-specific value beyond summarizing the return format as 'same fields as the single lookup'.

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?

Description clearly states the verb 'Look up', resource 'geolocation data', and scope 'up to 50,000 IP addresses or hostnames'. It distinguishes from the sibling 'ipgeolocation_lookup' by explicitly mentioning bulk and the limit.

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?

The description implies this tool is for multiple IPs, contrasting with a single lookup. However, it does not explicitly state when to prefer this over repeated single lookups or other alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/api-freaks/apifreaks-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server