Handled Locator
Server Details
Manage a store locator by chatting: locations, tags, booking buttons, map styling, embed code.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 28 tools
Most tools target a distinct resource+action, and descriptions actively cross-reference near-neighbours (set_custom_field explicitly excludes tags; tag_locations vs set_tag_style are clarified). The only real softness is find_nearest_locations, which also doubles as a data-query tool via `tag`/`q`, overlapping list_locations and list_tags, and the tag/custom-field trio requires reading descriptions to separate.
Every tool is snake_case with a leading verb (list_/get_/create_/update_/delete_/set_/publish_/apply_/propose_), and pluralization is used consistently for batch operations (`ids`, `locations`, `territories`). No camelCase or style mixing anywhere in the set.
28 tools is heavy for a single locator product, though the surface genuinely spans five subsystems (locations, territories, spotlight rules, configuration, tags/fields), so the count is not arbitrary. A few thin tools (get_embed_code, set_spotlight_rule_enabled, list_tags) could fold into siblings to bring it under the comfortable range.
CRUD is complete for locations, spotlight rules, and configuration (with a propose/apply/rollback lifecycle that is unusually thorough), and territories cover create/add-postcodes/publish/mode/ownership-explanation. Gaps are minor: no single-territory or single-rule getter, no territory rename/re-owner, and no analytics or reporting surface for a product whose soft delete is explicitly justified by analytics history.
Available Tools
28 toolsadd_territory_postcodesAdd postcodes to a territoryAInspect
Grant (include) or carve out (exclude) postcodes for a territory. Not live until publish_territories.
Inputs: id (required), postcodes (required), op.
apply_configurationApply a configuration proposalADestructiveInspect
Make a prepared proposal live on the customer's website. Only call this after showing the person the differences from propose_configuration and getting their agreement. Refused if the locator changed since the proposal was prepared.
Inputs: proposalId (required).
create_locationAdd a locationAInspect
Add one location, or many in a single call. A plain address is geocoded automatically, so lat and lng are only needed to override the result. Pass locations with an array to add a batch: adding ten showrooms is one call, not ten, and the reply says exactly which ones landed. Counts against the plan's location allowance.
Inputs: lat, lng, city, name, +22 more.
create_spotlight_ruleCreate a Spotlight ruleAInspect
Add a rule with one trigger (when it applies) and one action (what the visitor sees), switched on immediately and applied after the existing rules. Location ids come from list_locations.
Inputs: name (required), actionKind (required), triggerKind (required), endsAt, +3 more.
create_territoryCreate a territoryAInspect
Create an empty territory owned by one location (dealer). It covers nothing until postcodes are added with add_territory_postcodes, and nothing reaches a visitor until publish_territories. Polygons and regions are drawn on the map in the dashboard.
Inputs: name (required), locationId (required), rank, exclusive.
delete_locationDelete a location, or many at onceADestructiveIdempotentInspect
Remove a location from the locator. This is a soft delete: the row is retained so analytics history stays intact, and it can be restored from the dashboard. Pass ids instead of id to delete up to 200 in one call.
Inputs: id, ids.
delete_spotlight_ruleDelete a Spotlight ruleADestructiveIdempotentInspect
Delete a rule. It stops applying at once and cannot be restored. Get the id from list_spotlight_rules.
Inputs: id (required).
delete_territoryDelete a territoryADestructiveIdempotentInspect
Delete a territory and its rules. Visitors keep being routed by the published version until publish_territories runs again.
Inputs: id (required).
describe_configurationDescribe the locator configurationARead-onlyIdempotentInspect
The current value of everything on the locator, with the schema beside it: behaviour settings, brand tokens, result-card layouts and visitor-facing wording. Use it to read what is set now. To write a change you do not need it: propose_configuration's own input schema lists every key and allowed value. Pass section to get one part instead of all 30KB.
Inputs: section.
explain_territory_ownerExplain who owns a pointARead-onlyIdempotentInspect
Which dealer owns a point, and why, answered from the PUBLISHED territories, exactly as a visitor there would be routed.
Inputs: lat (required), lng (required), postcode.
find_nearest_locationsFind the nearest locationsARead-onlyIdempotentInspect
Rank locations by distance from a point, the way the widget ranks them for a visitor. Also answers questions about the data when given tag or q without a point.
Inputs: q, lat, lng, tag, +4 more.
get_embed_codeGet the embed codeARead-onlyIdempotentInspect
The HTML snippet that puts this locator on a website, plus the public site id it carries. Paste it where the map should appear.
Inputs: near, tags.
get_locationGet a locationARead-onlyIdempotentInspect
Full details for one location, including hours and custom fields.
Inputs: id (required).
list_configuration_versionsList configuration historyARead-onlyIdempotentInspect
The locator's configuration history, newest first, with what caused each version. Use it to find a version number to roll back to.
Inputs: limit.
list_locationsList locationsARead-onlyIdempotentInspect
List the locations on this locator, newest first. Use search to find one by name or address before editing it.
Inputs: limit, offset, search, visibility.
list_spotlight_rulesList Spotlight rulesARead-onlyIdempotentInspect
Spotlight rules change what a visitor sees depending on where and when they search: a banner for a region or a date range, featured locations, only certain locations, or hidden ones. Lists every rule in the order they apply (after territories), with ids. Call this before changing a rule.
Inputs: no named parameters.
list_tagsList tagsARead-onlyIdempotentInspect
The tags (categories) on this locator, with how many locations carry each one. Tags are what visitors filter by on the map.
Inputs: no named parameters.
list_territoriesList dealer territoriesARead-onlyIdempotentInspect
Who OWNS an address, as distinct from who can reach it: a service radius says how far a location travels, a territory decides which dealer an enquiry belongs to. Lists every territory with its owner, rank, rules and id, the territory mode, and the published version. Nothing reaches a visitor until publish_territories.
Inputs: no named parameters.
propose_configurationPropose a configuration changeAInspect
Prepare a change to how the locator looks or behaves, WITHOUT applying it. Returns the exact list of differences. Show that list to the person and get their agreement before calling apply_configuration. This tool's input schema lists every key and every allowed value, so write the patch straight from it; a rejected patch names every wrong key and value at once. Only send the keys you want to change.
Inputs: request (required), summary (required), labels, layouts, +2 more.
publish_territoriesPublish territoriesADestructiveIdempotentInspect
Make the current territories live. Writes a new version and replaces what visitors are routed by once every file is written.
Inputs: no named parameters.
rollback_configurationRoll back the configurationADestructiveInspect
Restore a previous configuration version. This creates a new version rather than erasing history, so a rollback can itself be rolled back.
Inputs: targetVersion (required).
set_custom_fieldSet a custom field across locationsADestructiveIdempotentInspect
Put the same extra field on many locations at once: a booking button, a social link, or a labelled fact like "Parking: street only". A value that is a URL becomes a clickable button; anything else shows as plain text. NOT for tags or categories, which are a different thing entirely: use tag_locations for those. Set remove to true to take the field off instead.
Inputs: key (required), locationIds (required), icon, color, +3 more.
set_spotlight_rule_enabledSwitch a Spotlight rule on or offAIdempotentInspect
Turn a rule on or off without deleting it. Get the id from list_spotlight_rules.
Inputs: id (required), enabled (required).
set_tag_styleStyle a tagADestructiveIdempotentInspect
Change how an existing tag looks on the map's filters: its filter group, chip colour and icon. Only the fields you pass are changed. Tags in the same group show as one labelled filter dropdown. Use the exact tag name. The tag must already exist; to create a tag and style it at once, use tag_locations.
Inputs: tag (required), icon, color, group.
set_territory_modeSet how territories applyAIdempotentInspect
Choose how territories affect a visitor's results: off, preferred, exclusive or fallback. Applies to the live locator straight away.
Inputs: mode (required).
tag_locationsTag or untag locationsADestructiveIdempotentInspect
Add a tag to locations, or remove it from them with action "remove". Adding creates the tag if it does not exist yet. Tags appear as filter chips that visitors use on the map. When adding, you can also pass group, color or icon to style the tag in the same call. Use this for requests like "tag these as X" or "mark these as X"; tags are not custom fields. Get location ids from list_locations first.
Inputs: tag (required), locationIds (required), icon, color, +2 more.
update_locationUpdate a location, or many at onceADestructiveIdempotentInspect
Change one or more fields on an existing location. Only the fields you send are touched. Changing the address re-geocodes it. Pass ids instead of id to apply the same fields to many locations in one call, for example hiding a batch or setting priority across a region; address, coordinates and name stay one-at-a-time.
Inputs: id, ids, lat, lng, +23 more.
update_spotlight_ruleUpdate a Spotlight ruleADestructiveIdempotentInspect
Replace a rule's name, trigger, action and dates. Send the whole rule, not only the changed part: the previous values are overwritten. Get the id from list_spotlight_rules.
Inputs: id (required), name (required), actionKind (required), triggerKind (required), +4 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Set up your store locator from AI: add stores, get the install code, see what visitors search for.
Build interactive maps for your website from a chat: places, routes, filters, cards, embed code.
Run a local business from your AI app: bookings, customers, inbox, website, posts and payments.
Live chat and AI agent for websites: answer visitors, manage sites, the AI agent and stats.
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables managing Google Business Profiles through natural language: list locations, reply to reviews, create local posts, and fetch performance metrics.26344 npm3MIT
- AlicenseNot gradedqualityBmaintenanceEnables managing AI voice agents, phones, integrations, workflows, calls, and billing directly from chat, including editing agent settings, connecting CRMs, and reviewing call logs.MIT
- AlicenseNot gradedqualityBmaintenanceLets coding agents add working maps to apps by creating API keys, geocoding and reverse-geocoding addresses, getting MapLibre snippets for HTML, React, Vue or Svelte, and monitoring or lowering prepaid usage budgets.83 npmMIT
- AlicenseAqualityBmaintenanceEnables AI assistants to search places and addresses, compute driving, walking, and kickboard routes, optimize waypoints, and calculate distance and time matrices. Results can be displayed as interactive maps within conversations.1267 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.