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, returning location, ISP, and more. Individual failures don't block results.

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
fieldsNoComma-separated dot-path fields to include in the response (allowlist). E.g. 'location.city,asn.organization'.
includeNoAdditional data modules to include. Available: security, hostname, liveHostname, hostnameFallbackLive, user_agent, abuse, dma_code, geo_accuracy. Use '*' to include all modules. Note: 'security' and 'abuse' fields cost extra credits.
excludesNoComma-separated dot-path fields to exclude from the response (denylist). E.g. 'location.city,asn.organization'.
Behavior5/5

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

Description discloses max batch size (50,000) and error behavior (failure includes 'message' field, non-blocking), adding value beyond annotations (readOnlyHint, idempotentHint, etc.). No contradictions found.

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?

Three sentences, front-loaded with purpose, no unnecessary words. Efficient and structured.

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 no output schema, description notes return is 'array of geolocation objects — same fields as the single lookup', which assumes knowledge of sibling tool. This is acceptable but slightly incomplete for an agent unfamiliar with the single lookup.

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%, so baseline is 3. Description does not add further meaning to parameters beyond schema. The mention of 'individual IP failures' relates to output, not parameters.

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?

Clearly states it performs bulk geolocation lookup for up to 50,000 IPs/hostnames, distinguishing from the single lookup sibling (ipgeolocation_lookup). The verb 'look up' and resource 'geolocation data' are specific.

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?

Implies when to use (need many IPs) and mentions failure handling (individual failures don't block others). Does not explicitly state when not to use, but the bulk nature makes usage context clear.

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