Skip to main content
Glama
mysleekdesigns

CrawlForge MCP Server

localization

Look up a country's language, Accept-Language, timezone, currency and date formats, or run a country-targeted search. Returns values only — pass them to your fetch or search tool.

Instructions

Use this to look up the locale settings of a country - language, Accept-Language header, timezone, currency, search domain, date and number formats - or to run a search targeted at a country (operation:"localize_search"). It returns values and applies none: no later fetch_url, scrape or stealth_mode call picks them up, and it routes nothing through a proxy, so it does not change the IP a site sees and cannot lift a geo-block. Pass the returned values to the tool that makes the request: fetch_url headers:{"Accept-Language": acceptLanguage}; stealth_mode stealthConfig:{locale: language, timezone: timezone}; search_web localization:{countryCode, language}. scrape has no locale parameter. Not for an ordinary page read (scrape). Cost: 2 credits. Example: localization({operation:"configure_country", countryCode:"DE", language:"de"})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL — required for handle_geo_blocking; for auto_detect it is optional metadata used only as a TLD country hint (the page is never fetched)
contentNoPage content (HTML or plain text) to analyze — required for auto_detect; no fetching is performed
currencyNoISO 4217 currency code (e.g. 'USD', 'EUR') - configure_country only
languageNoLanguage code (e.g. 'en', 'fr', 'de-CH') - configure_country only; other values are refused
responseNoHTTP response for geo-blocking analysis
timezoneNoIANA timezone identifier (e.g. 'America/New_York') - configure_country and generate_timezone_spoof
operationNoLocalization operation to perform. Every operation returns data; none changes how another tool behaves. configure_country: the country's settings (language, acceptLanguage, timezone, currency, searchDomain, browserLocale). localize_search: runs search_web for searchParams.query in the country and its language. localize_browser: Playwright-style context options for the country (locale, timezoneId, geolocation, extraHTTPHeaders) - no browser is launched. generate_timezone_spoof: a JavaScript snippet that overrides Date and Intl for the timezone - nothing is injected. handle_geo_blocking: classifies a response you supply (url + response) and lists suggestions - nothing is fetched or bypassed. auto_detect: language and country detected in content you supply. get_stats: counters for this server process. get_supported_countries: the accepted country codes.configure_country
userAgentNoNot used by any operation. To carry a user agent through localize_browser, set browserOptions.userAgent
countryCodeNoISO 3166-1 alpha-2 country code, upper or lower case; operation:"get_supported_countries" lists the accepted ones. When omitted, the other operations use the country of the last configure_country call in this server process (US at start) - pass it on every call
geoLocationNoCoordinates echoed back in the configure_country result; nothing is emulated
searchParamsNoSearch parameters for localized search queries
customHeadersNoHeaders echoed back in the configure_country result; nothing is sent
proxySettingsNoEchoed back in the configure_country result. No request is routed through it: CrawlForge supplies no proxies, and your own go on stealth_mode stealthConfig.proxyRotation
acceptLanguageNoAccept-Language value to return from configure_country in place of the one built from the language and country
browserOptionsNoBrowser context options for localize_browser to build on: returned with the country's locale, timezoneId, geolocation and Accept-Language set, and your userAgent and other extraHTTPHeaders kept

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv6.18.1
    • changedInput schema / properties / acceptLanguage / description
      Previous value: -"Accept-Language header value"New value: +"Accept-Language value to return from configure_country in place of the one built from the language and country"
    • changedInput schema / properties / browserOptions / description
      Previous value: -"Browser context options for locale emulation"New value: +"Browser context options for localize_browser to build on: returned with the country's locale, timezoneId, geolocation and Accept-Language set, and your userAgent and other extraHTTPHeaders kept"
    • changedInput schema / properties / countryCode / description
      Previous value: -"ISO 3166-1 alpha-2 country code"New value: +"ISO 3166-1 alpha-2 country code, upper or lower case; operation:\"get_supported_countries\" lists the accepted ones. When omitted, the other operations use the country of the last configure_country call in this server process (US at start) - pass it on every call"
    • changedInput schema / properties / currency / description
      Previous value: -"ISO 4217 currency code (e.g. 'USD', 'EUR')"New value: +"ISO 4217 currency code (e.g. 'USD', 'EUR') - configure_country only"
    • changedInput schema / properties / customHeaders / description
      Previous value: -"Custom HTTP headers for localized requests"New value: +"Headers echoed back in the configure_country result; nothing is sent"
    • changedInput schema / properties / geoLocation / description
      Previous value: -"GPS coordinates for geolocation emulation"New value: +"Coordinates echoed back in the configure_country result; nothing is emulated"
    • changedInput schema / properties / language / description
      Previous value: -"Language code (e.g. 'en', 'fr', 'de')"New value: +"Language code (e.g. 'en', 'fr', 'de-CH') - configure_country only; other values are refused"
    • changedInput schema / properties / operation / description
      Previous value: -"Localization operation to perform"New value: +"Localization operation to perform. Every operation returns data; none changes how another tool behaves. configure_country: the country's settings (language, acceptLanguage, timezone, currency, searchDomain, browserLocale). localize_search: runs search_web for searchParams.query in the country and its language. localize_browser: Playwright-style context options for the country (locale, timezoneId, geolocation, extraHTTPHeaders) - no browser is launched. generate_timezone_spoof: a JavaScript snippet that overrides Date and Intl for the timezone - nothing is injected. handle_geo_blocking: classifies a response you supply (url + response) and lists suggestions - nothing is fetched or bypassed. auto_detect: language and country detected in content you supply. get_stats: counters for this server process. get_supported_countries: the accepted country codes."
    • changedInput schema / properties / proxySettings / description
      Previous value: -"Proxy configuration for geo-targeted requests"New value: +"Echoed back in the configure_country result. No request is routed through it: CrawlForge supplies no proxies, and your own go on stealth_mode stealthConfig.proxyRotation"
    • changedInput schema / properties / timezone / description
      Previous value: -"IANA timezone identifier (e.g. 'America/New_York')"New value: +"IANA timezone identifier (e.g. 'America/New_York') - configure_country and generate_timezone_spoof"
    • changedInput schema / properties / userAgent / description
      Previous value: -"Custom user agent string"New value: +"Not used by any operation. To carry a user agent through localize_browser, set browserOptions.userAgent"
  2. Changed11 schema fields changedv6.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / browserOptions / additionalProperties
      Removed value: -false
    • addedInput schema / properties / browserOptions / properties / extraHTTPHeaders / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / customHeaders / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / geoLocation / additionalProperties
      Removed value: -false
    • removedInput schema / properties / proxySettings / additionalProperties
      Removed value: -false
    • removedInput schema / properties / proxySettings / properties / fallback / additionalProperties
      Removed value: -false
    • removedInput schema / properties / proxySettings / properties / rotation / additionalProperties
      Removed value: -false
    • removedInput schema / properties / response / additionalProperties
      Removed value: -false
    • removedInput schema / properties / searchParams / additionalProperties
      Removed value: -false
    • addedInput schema / properties / searchParams / properties / headers / propertyNames
      Added value: +{
      +  "type": "string"
      +}
  3. Changed3 schema fields changedv5.0.4
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / content / description
      Previous value: -"Content for auto-detection of language and locale"New value: +"Page content (HTML or plain text) to analyze — required for auto_detect; no fetching is performed"
    • changedInput schema / properties / url / description
      Previous value: -"URL for geo-blocking detection or auto-detection"New value: +"URL — required for handle_geo_blocking; for auto_detect it is optional metadata used only as a TLD country hint (the page is never fetched)"
  4. First observedv4.10.0

TDQS

A4.9/5.0
Behavior5/5

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

Discloses the single most surprising trait — the tool applies nothing: no later fetch_url/scrape/stealth_mode call picks up the values, nothing routes through a proxy, the IP is unchanged and geo-blocks are not lifted. It also states the cost (2 credits). These are exactly the side-effect expectations an agent would otherwise wrongly assume from a 'configure' operation.

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?

Front-loaded with the purpose and the critical no-side-effect constraint, then the value-routing recipe, the exclusion, and cost. Dense but every clause earns its place for a 15-parameter, 8-operation tool; nothing is redundant.

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?

Given 15 parameters, nested objects, 8 enum operations, no output schema and an open-world hint, the description covers return semantics, side-effect profile, cost, and how values flow to named siblings. An agent has everything needed to select and invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema carries the per-parameter detail and the baseline is 3. The description goes beyond it with the credential-relevant advice to 'pass countryCode on every call' (since omitted calls silently reuse the last configure_country state), plus a worked example and the per-operation return descriptions.

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?

States a specific verb and resource — 'look up the locale settings of a country' and 'run a search targeted at a country' — and immediately differentiates from siblings by naming the two operations and their outputs (language, Accept-Language, timezone, currency, etc.). The closing example call pins the shape down concretely.

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

Usage Guidelines5/5

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

Explicit about when to use it (setting up locale for a request), when not to ('Not for an ordinary page read (scrape)'), and which alternatives to route results to (fetch_url headers, stealth_mode stealthConfig, search_web localization). It even notes scrape has no locale parameter, ruling out a misuse path.

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