Handled Locator

Update a location, or many at once

update_location

DestructiveIdempotent

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.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	Location id.
`ids`	No	Several location ids, to apply the same change to all of them in one call (at most 200). Use either id or ids.
`lat`	No	Latitude. Supplying lat and lng skips geocoding.
`lng`	No	Longitude.
`city`	No
`name`	No	Business or store name.
`email`	No
`hours`	No	Opening hours keyed by ISO weekday, 1 = Monday. Each value is ONE {open, close} in 24h HH:MM, or null for closed — not a list, and a list is rejected. Example: {"1": {"open": "09:00", "close": "17:00"}, "7": null}. REPLACES the whole week: any day left out is cleared. To change one day without restating the rest, use hoursPatch.
`phone`	No
`state`	No
`address`	No	Full address as a person would write it. Geocoded automatically unless lat and lng are supplied.
`website`	No
`imageUrl`	No
`priority`	No	Higher sorts first when there is no visitor position.
`timezone`	No	IANA timezone, for example America/Chicago.
`hoursPatch`	No	Change only the days named, leaving every other day exactly as it is. Same shape as hours but partial: {"7": {"open": "10:00", "close": "16:00"}} changes Sunday alone, and {"7": null} closes it. Use this to edit hours; it cannot silently revert a day you did not mention. Ignored if hours is also sent.
`postalCode`	No
`visibility`	No	hidden keeps the location in the account but off the public locator.
`countryCode`	No	Two-letter ISO country code.
`description`	No
`markerColor`	No	Hex colour for this location's map marker.
`addressLine1`	No	Street line, when the address is structured.
`customFields`	No	Extra fields, keyed by the label shown to visitors. The value is either a plain string, or an object {value, color, icon, style} where `value` is the URL or text. There is no `label` or `url` key: the label is the key, and the URL goes in `value`. Example: {"Book a table": {"value": "https://example.com/book", "color": "#C2540E"}}. Never use this for tags or categories; use the categories field instead.
`locationType`	No	point is a physical address, service_area covers a radius, online is a stockist with no address.
`onlineRegions`	No	For an online location: two-letter country codes it ships to or serves, e.g. ["us", "ca"]. Empty means every visitor sees it.
`serviceRadiusKm`	No	Radius in km, for a service_area location.
`serviceAreaCircleVisible`	No	For a service_area location: whether to draw its coverage circle. Null (the default) follows the locator's serviceAreaCircleVisible setting. False draws the pin without the circle.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 20, 2026

changedInput schema / properties / hours / description

Previous value: -"Opening hours keyed by ISO weekday, 1 = Monday. Each value is a list of {open, close} in 24h HH:MM, or null for closed. REPLACES the whole week: any day left out is cleared. To change one day without restating the rest, use hoursPatch."New value: +"Opening hours keyed by ISO weekday, 1 = Monday. Each value is ONE {open, close} in 24h HH:MM, or null for closed — not a list, and a list is rejected. Example: {\"1\": {\"open\": \"09:00\", \"close\": \"17:00\"}, \"7\": null}. REPLACES the whole week: any day left out is cleared. To change one day without restating the rest, use hoursPatch."

changedInput schema / properties / hoursPatch / description

Previous value: -"Change only the days named, leaving every other day exactly as it is. Same shape as hours but partial: {\"7\": [{\"open\": \"10:00\", \"close\": \"16:00\"}]} changes Sunday alone. Use this to edit hours; it cannot silently revert a day you did not mention. Ignored if hours is also sent."New value: +"Change only the days named, leaving every other day exactly as it is. Same shape as hours but partial: {\"7\": {\"open\": \"10:00\", \"close\": \"16:00\"}} changes Sunday alone, and {\"7\": null} closes it. Use this to edit hours; it cannot silently revert a day you did not mention. Ignored if hours is also sent."

Changed3 schema fields changedSep 20, 2026

changedInput schema / properties / hours / description

Previous value: -"Opening hours keyed by ISO weekday, 1 = Monday. Each value is a list of {open, close} in 24h HH:MM, or null for closed."New value: +"Opening hours keyed by ISO weekday, 1 = Monday. Each value is a list of {open, close} in 24h HH:MM, or null for closed. REPLACES the whole week: any day left out is cleared. To change one day without restating the rest, use hoursPatch."

addedInput schema / properties / hoursPatch

Added value: +{
+  "description": "Change only the days named, leaving every other day exactly as it is. Same shape as hours but partial: {\"7\": [{\"open\": \"10:00\", \"close\": \"16:00\"}]} changes Sunday alone. Use this to edit hours; it cannot silently revert a day you did not mention. Ignored if hours is also sent.",
+  "type": "object"
+}

addedInput schema / properties / serviceAreaCircleVisible

Added value: +{
+  "description": "For a service_area location: whether to draw its coverage circle. Null (the default) follows the locator's serviceAreaCircleVisible setting. False draws the pin without the circle.",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

Changed1 schema field changedSep 19, 2026

addedInput schema / properties / onlineRegions

Added value: +{
+  "description": "For an online location: two-letter country codes it ships to or serves, e.g. [\"us\", \"ca\"]. Empty means every visitor sees it.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed2 schema fields changedSep 18, 2026

addedInput schema / properties / ids

Added value: +{
+  "description": "Several location ids, to apply the same change to all of them in one call (at most 200). Use either id or ids.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 200,
+  "type": "array"
+}

removedInput schema / required
```
Removed value: -[
-  "id"
-]
```

First observedSep 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description discloses meaningful behavioral details beyond the annotations: only sent fields are touched, changing the address triggers re-geocoding, and batch updates apply the same fields to many locations. It does not expand on the destructive implications hinted by destructiveHint=true, but it does not contradict that annotation either.

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?

The description is compact: three sentences, no fluff, with the core partial-update behavior first and batching details second. Every sentence adds information an agent needs before calling the tool.

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?

For a 27-parameter mutating tool with no output schema, the description plus rich schema is largely sufficient. It covers partial updates, re-geocoding, and batch constraints; the only omissions are explicit return behavior and consequences of destructiveHint=true, which are not strictly needed for selecting and invoking the tool.

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?

With 70% schema coverage, the schema already documents many parameters, and the description adds important cross-parameter semantics: `ids` vs `id`, one-at-a-time address/coordinates/name, and automatically skipping geocoding when lat/lng are supplied. This is useful beyond the schema, though the description intentionally leaves detailed per-field behavior to the schema.

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?

The first sentence states a specific action and target: 'Change one or more fields on an existing location.' This clearly distinguishes the tool from siblings like create_location, delete_location, and get_location. The title also communicates batch capability immediately.

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 explains when to use `ids` instead of `id`, and notes that address, coordinates, and name stay one-at-a-time. It does not explicitly contrast with create/delete/other siblings, but the existing-location scope and clear batching guidance provide strong usage context.

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

All Handled Locator tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?