Skip to main content
Glama
mapbox

Mapbox Developer MCP Server

Official
by mapbox

Retrieve Mapbox Style Tool

retrieve_style_tool
Read-onlyIdempotent

Retrieve a specific Mapbox style by its ID for use in map customization and API integration.

Instructions

Retrieve a specific Mapbox style by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
styleIdYesStyle ID to retrieve

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUnique style identifier
fogNoFog properties
nameYesHuman-readable name for the style
zoomNoDefault zoom level
draftNoWhether this is a draft version
lightNoGlobal light source (deprecated, use lights)
ownerYesUsername of the style owner
pitchNoDefault pitch in degrees
centerNoDefault map center [longitude, latitude]
glyphsNoURL template for glyph sets
layersYesLayers in draw order
lightsNoArray of 3D light sources
spriteNoBase URL for sprite image and metadata
bearingNoDefault bearing in degrees
createdYesISO 8601 timestamp when style was created
importsNoImported styles
sourcesYesData source specifications
terrainNoGlobal terrain elevation
versionYesStyle specification version number. Must be 8
metadataNoArbitrary properties for tracking
modifiedYesISO 8601 timestamp when style was last modified
protectedNoWhether style is protected from modifications
projectionNoMap projection
transitionNoDefault transition timing
visibilityYesStyle visibility setting
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description does not add further behavioral context, but it does not contradict annotations.

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?

A single sentence of 8 words with no filler, front-loading the key information.

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

Completeness3/5

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

For a simple read operation with one parameter and an existing output schema, the description is minimally adequate. However, it does not explain what 'retrieve' returns or differentiate from similar tools like preview_style_tool.

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 coverage is 100% and the parameter 'styleId' is already described in the schema. The tool description adds no additional meaning beyond 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 description 'Retrieve a specific Mapbox style by ID' uses a specific verb and resource, clearly distinguishing it from siblings like list_styles_tool or create_style_tool.

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 guidance is provided on when to use this tool versus alternatives such as preview_style_tool or list_styles_tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mapbox/mcp-devkit-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server