Skip to main content
Glama

Create map poster

create_poster
Read-onlyIdempotent

Designs a map poster of a real place and shows a preview of it in the chat. Use this when the user wants a map poster, map print or map wall art of a place, for their home or as a gift (for example, a map of where a couple met). Takes a city, neighborhood, address, landmark or coordinates (up to three places on one poster), a style from list_themes, the poster text, pins, a driving route and a shape; the link it returns opens the design in the MapPoster editor, where it can be adjusted, downloaded as a PNG or, in the drawn map styles, ordered printed. Give a place or lat/lon; the rest is optional. Nothing is saved or bought: the design lives in the link. Not for general gift advice, directions, travel plans, star maps, photo posters, or running, walking or GPX routes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
latNoLatitude of the map centre.
lonNoLongitude of the map centre.
matNoGallery-style mat (passe-partout) around the map.
sizeNoCanvas size preset: poster_portrait (1080×1527), poster_landscape (1527×1080), square (1080×1080), instagram_portrait (1080×1350), story (1080×1920), pinterest (1000×1500), desktop_wallpaper (1920×1080), a4 (2480×3508), a3 (3508×4961), a2 (4961×7016), 18x24in (5400×7200). Default poster_portrait.
zoomNoZoom: ~11 metro area, 13 city, 15 neighbourhood, 16-17 a few streets. Default: the suggested zoom for the place.
placeNoThe place the user wants on the poster, e.g. "Utrecht" or "Brooklyn, New York". Used when lat/lon are not given (first search match).
routeNoThe driving route between two points, e.g. a road trip, through up to 10 via points. It follows the roads by car: not for running, walking or GPX routes.
shapeNoMap shape (default rectangle); circle, hexagon and heart make the canvas square.
themeNoTheme key (see list_themes). standard and satellite are classic map tiles for personal use; all others are artistic vector styles.mediterranean_sun
titleNoMain poster text: the user's own words if they give them, otherwise in their language. Default: the place name. Can be personal, e.g. "WHERE IT ALL BEGAN" or two names.
widthNoCustom canvas width in px (overrides size).
heightNoCustom canvas height in px (overrides size).
text_xNoHorizontal text position, 0-1 (default 0.5).
text_yNoVertical text position, 0-1 (default 0.85).
bearingNoMap rotation in degrees (default 0, north up).
markersNoPins on the map, e.g. a home or the spot where a couple met.
languageNoLanguage for place names, e.g. "nl" or "de" (default "en"). Use the user's language.
subtitleNoSecond line: the user's own words if they give them, otherwise in their language. Default: the country. Can be a date or a short message.
mat_widthNoMat width in px (default 40).
text_sizeNoSize of the text block (default medium); "none" hides all text.
mat_borderNoThin line around the map inside the mat (default on).
show_parksNoArtistic themes only.
show_roadsNoArtistic themes only.
show_waterNoArtistic themes only.
title_boldNo
title_caseNoDefault uppercase.
title_fontNoDefault Playfair Display.
coordinatesNoCustom text for the coordinates line. Default: the map centre coordinates.
marker_iconNoDefault pin.
marker_sizeNoMarker size in px (default 40).
more_placesNoUp to two more places on the same poster, each with its own map and a label under it, e.g. where a couple met, got engaged and married. The first map is `place` (or lat/lon); markers and the route stay on it. Artistic themes only; the maps are rectangular (shape is ignored) and the title sits under them (text_x/text_y are ignored).
place_labelNoWith more_places: the label under the first map, in the user's words or language. Default: its place name.
route_colorNoRoute colour as #RRGGBB. Default: the theme route colour.
marker_colorNoMarker colour as #RRGGBB. Default: the theme accent.
white_borderNoWhite frame around the map.
places_layoutNoWith more_places: the maps stacked or side by side. Default auto: side by side on a landscape or square poster, else stacked.
show_subtitleNo
subtitle_fontNoDefault Playfair Display.
show_buildingsNoArtistic themes only.
show_map_labelsNoStreet, place and water names on the map, for the themes that offer them (midnight_dark, minimal_white, modern_voyager). Default on.
text_backgroundNoShading behind the text for readability (default none). Not used with a shape: a heart, circle or hexagon keeps its own edge.
title_font_sizeNoTitle size in px; 0 = automatic (default).
coordinates_fontNoDefault Outfit.
show_coordinatesNo
title_letter_spacingNoTitle letter spacing in px (default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / properties / markers / items / properties / lat / description
      Added value: +"Latitude, -90 to 90."
    • addedInput schema / properties / markers / items / properties / lon / description
      Added value: +"Longitude, -180 to 180."
    • changedInput schema / properties / route / description
      Previous value: -"A route along the roads (driving directions) from start to end, through up to 10 via points: a road trip, or a road race such as a marathon, traced through points along its course."New value: +"The driving route between two points, e.g. a road trip, through up to 10 via points. It follows the roads by car: not for running, walking or GPX routes."
    • addedInput schema / properties / route / properties / end / description
      Added value: +"Where the route ends."
    • addedInput schema / properties / route / properties / end / properties / lat / description
      Added value: +"Latitude, -90 to 90."
    • addedInput schema / properties / route / properties / end / properties / lon / description
      Added value: +"Longitude, -180 to 180."
    • addedInput schema / properties / route / properties / start / description
      Added value: +"Where the route starts."
    • addedInput schema / properties / route / properties / start / properties / lat / description
      Added value: +"Latitude, -90 to 90."
    • addedInput schema / properties / route / properties / start / properties / lon / description
      Added value: +"Longitude, -180 to 180."
    • addedInput schema / properties / route / properties / via / description
      Added value: +"Up to 10 points the route passes through, in order."
    • addedInput schema / properties / route / properties / via / items / properties / lat / description
      Added value: +"Latitude, -90 to 90."
    • addedInput schema / properties / route / properties / via / items / properties / lon / description
      Added value: +"Longitude, -180 to 180."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint true and destructiveHint false, but the description adds what those hints cannot convey: nothing is persisted or purchased, the design lives entirely in the returned link, the link opens the MapPoster editor, and printing is only available for drawn styles. That resolves the ambiguity in "ordered printed", which could otherwise be mistaken for a real-world purchase side effect.

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?

Front-loaded with purpose, then usage, then a compact inventory of inputs, then limits — a sensible order for a 45-parameter tool. The middle sentence packs a lot into one clause chain, but nearly every clause adds distinct information rather than restating the schema.

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 45-parameter, deeply nested tool with no output schema, the description covers the essentials an agent needs: required input, what the return value is, non-persistence, and the editing/printing follow-up. Remaining omissions, such as error behavior when a place name fails to resolve, are minor against a schema that documents 93% of fields.

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 93%, so the schema carries most parameter meaning and the baseline would be 3. The description still adds value by explaining the relationship between parameters — up to three places on one poster, the route being car-only, and style coming from list_themes — which is cross-field context the schema does not state in one place.

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?

Opens with a specific verb and resource: "Designs a map poster of a real place and shows a preview of it in the chat." It clearly distinguishes itself from siblings by pointing to list_themes for styles and by scoping to poster design rather than location lookup, so an agent can route between them without opening any schema.

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?

Gives an explicit trigger ("Use this when the user wants a map poster, map print or map wall art... for their home or as a gift") with a concrete example, plus a strong exclusion list ("Not for general gift advice, directions, travel plans, star maps, photo posters, or running, walking or GPX routes"). It also states the minimum viable call: "Give a `place` or `lat`/`lon`; the rest is optional."

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources