GoodBarber

Create map

cms_create_map

Create map item. Guidance: Create one CMS map (point of interest) item from map category ids. | context: title, categories, address

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": {
      "title": "<title>",
      "categories": "<categories>",
      "address": "<address>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "cms_create_map"
  }
}

Input Schema

Name	Required	Description
`meta`	No	Optional SEO payload with title and description.
`slug`	No	Optional URL slug; the server may normalize it.
`email`	No	Optional contact email for the map point.
`title`	Yes	Map point name shown in feeds and on the item page.
`leadin`	No	Optional deck: short intro text placed at the start of the map point list excerpt. 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	Publication status. Omit on create to default to published. Do not send scheduled.
`address`	Yes	Street or place address of the point of interest. Required and non-empty.
`website`	No	Optional website URL for the map point.
`latitude`	Yes	Latitude of the point in decimal degrees; finite number.
`longitude`	Yes	Longitude of the point in decimal degrees; finite number.
`accessTier`	No	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`	Yes	Non-empty category id array. Use cms_list_cms_sections with type='maps' to discover map category ids.
`pinIconUrl`	No	Optional pin icon. Built-in choices: 1 = teardrop location marker (default), 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 on create to use built-in icon 1.
`phoneNumber`	No	Optional contact phone number for the map point.
`pinIconColor`	No	Optional pin tint as #RGB or #RRGGBB. Omit on create to use #e94f06. An empty string clears the tint.
`publishedDate`	No	Future ISO datetime for deferred publication. Requires status='stock' when provided.
`commentsEnabled`	No	Whether end-user comments are enabled for this map item.
`useThumbAsPinIcon`	No	Whether the map item thumbnail is used as the map pin icon. Stored as off on create; set a thumbnail via a photo paragraph first, then update this flag.
`publicationEndDate`	No	Future ISO datetime for scheduled unpublication.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.1/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds almost nothing beyond that: it does not mention permission/auth requirements, uniqueness constraints on slug or title, what happens on duplicate creation, or what the call returns (no output schema exists). The only extra signal is the "one item" cardinality hint.

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

Conciseness4/5

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

Two short, front-loaded lines with no filler; the purpose statement leads and the required-field summary follows. The pipe-delimited "| context:" formatting is slightly cryptic, but nothing is wasted.

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 19-parameter creation tool with a nested meta object and no output schema, the description should at least indicate what is returned (e.g., the new item's id) and any notable defaults or side effects. The schema covers per-field behavior well, but the description itself leaves the agent without return-value or post-create expectations.

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 every parameter — required, optional, defaults, enums, character limits — is documented in the schema itself. The description repeats only "title, categories, address" as context, adding no format, validation, or default information beyond what the schema supplies, so the baseline 3 applies.

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

Purpose4/5

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

The description names a specific verb and resource ("Create one CMS map (point of interest) item") and adds a scoping detail ("from map category ids"), which tells an agent this is a single top-level map item rather than a map paragraph. It does not explicitly contrast with cms_update_map or cms_create_map_paragraph, so it stops short of a 5.

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

Usage Guidelines3/5

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

"Create ONE ... item" implies per-item creation and no bulk path, and the required context fields narrow the use case, but there is no explicit when-not guidance (e.g., use cms_update_map for existing items, use paragraph tools to add content to the new map). Usage is inferable from the name and field list only.

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.