GoodBarber

Update map

cms_update_map

DestructiveIdempotent

Update map item. Guidance: Update one CMS map item by map item id. | context: id

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "cms_update_map"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Map item id returned by cms_list_maps.
`meta`	No	Optional SEO payload with title and description.
`slug`	No	Omit to keep the current slug; send to replace it.
`email`	No	Omit to keep the current contact email; send to replace it.
`title`	No	Omit to keep the current name; send to replace it.
`leadin`	No	Omit to keep the current deck; send to replace it. Plain text: HTML tags are removed, and so is the text after a bare '<' (write 'under 12', not '<12'). Not returned by read tools, and cleared when the map point is saved in the back office.
`status`	No	Omit to keep the current publication state. Do not send scheduled.
`address`	No	Omit to keep the current address; send a non-empty string to replace it.
`website`	No	Omit to keep the current website URL; send to replace it.
`latitude`	No	Omit to keep the current latitude; send a finite number to replace it.
`longitude`	No	Omit to keep the current longitude; send a finite number to replace it.
`accessTier`	No	Replacement paywall tier. 'premium' locks the item behind an in-app purchase; 'free' leaves it open. Applies only to apps that sell in-app purchases.
`categories`	No	Omit to keep placement. Send non-empty category ids to replace placement.
`pinIconUrl`	No	Replacement pin icon. Built-in choices: 1 = teardrop location marker, 2 = triangular flag, 3 = five-point star, 4 = pushpin, 5 = filled circle. For a custom pin, send an HTTP(S) image URL, raw base64 image, or image data URI. Omit to keep the current icon.
`phoneNumber`	No	Omit to keep the current contact phone number; send to replace it.
`pinIconColor`	No	Replacement pin tint as #RGB or #RRGGBB. Omit to keep the current tint; send an empty string to clear it.
`publishedDate`	No	Future ISO datetime for deferred publication. Requires status='stock' when provided.
`commentsEnabled`	No	Omit to keep the current comments setting; send true or false to replace it.
`useThumbAsPinIcon`	No	Whether the map item thumbnail is used as the map pin icon.
`publicationEndDate`	No	Future ISO datetime for scheduled unpublication. Send an empty string to clear an existing scheduled unpublication.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026
RemovedOct 8, 2026
First observedSep 8, 2026

TDQS

C2.5/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is carried by structured data. The description adds nothing the agent could not infer from that: it does not say that omitted fields are preserved while supplied fields replace current values, that scheduled statuses are rejected here, or what happens to leadin on back-office saves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but that brevity comes from under-specification rather than efficiency. The "| context: id" fragment reads as a generated artifact and the two sentences are redundant with each other.

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

Completeness2/5

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

For a 20-parameter, destructive, open-world mutation with no output schema, a two-sentence description is far too thin. The schema rescues field-level meaning, but the definition gives the agent no operational framing for a high-risk partial update.

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 description coverage is 100% and the 20 parameters carry detailed per-field semantics (omit-to-keep behavior, enum meanings, pin icon options, date constraints). The description only echoes "by map item id", adding no meaning beyond the schema, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Update map item" plus "Update one CMS map item by map item id" names a verb and resource, so an agent knows this is a partial update keyed by id. But the second sentence largely restates the first, and nothing in the text distinguishes it from siblings such as cms_update_map_paragraph; only the tool name does that work.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given beyond the circular "update one item by id". There is no mention of prerequisites, of how it relates to cms_get_map or cms_update_map_paragraph, or of when create/delete would be the right call instead.

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

All GoodBarber 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.