cesium-mcp

updateEntity

Idempotent

Update the position, appearance, label, visibility, or polygon extrusion height of an entity, including data-source entities. Returns { success: boolean, data?: unknown, message?: string, error?: string }.

Instructions

Input Schema

Name	Required	Description
`show`	No	Whether to show
`color`	No	New color (CSS format)
`label`	No	New label text
`scale`	No	New scale factor
`entityId`	Yes	Entity ID (returned by addMarker/addPolyline etc.)
`position`	No	New position coordinates
`sessionId`	No	Target browser session ID for multi-browser routing (optional)
`extrudedHeight`	No	Polygon extrusion height in meters; also supports GeoJSON data-source polygons

Output Schema

Name	Required	Description	Default
`data`	No
`error`	No
`message`	No
`success`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.139.23Oct 21, 2026

addedInput schema / properties / extrudedHeight

Added value: +{
+  "description": "Polygon extrusion height in meters; also supports GeoJSON data-source polygons",
+  "maximum": 100000,
+  "minimum": 0,
+  "type": "number"
+}

Changed1 schema field changedv1.139.19Aug 19, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "data": {},
+    "error": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv1.139.18Aug 12, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
Changed16 schema fields changedv1.139.17Jul 29, 2026
- addedInput schema / properties / color / maxLength
```
Added value: +64
```
- addedInput schema / properties / color / minLength
```
Added value: +1
```
- addedInput schema / properties / entityId / maxLength
```
Added value: +200
```
- addedInput schema / properties / entityId / minLength
```
Added value: +1
```
- addedInput schema / properties / label / maxLength
```
Added value: +200
```
- removedInput schema / properties / position / properties / height / description
```
Removed value: -"高度（米）"
```
- addedInput schema / properties / position / properties / height / maximum
```
Added value: +50000000
```
- addedInput schema / properties / position / properties / height / minimum
```
Added value: +-12000
```
- removedInput schema / properties / position / properties / latitude / description
```
Removed value: -"纬度（-90 ~ 90）"
```
- addedInput schema / properties / position / properties / latitude / maximum
```
Added value: +90
```
- addedInput schema / properties / position / properties / latitude / minimum
```
Added value: +-90
```
- removedInput schema / properties / position / properties / longitude / description
```
Removed value: -"经度（-180 ~ 180）"
```
- addedInput schema / properties / position / properties / longitude / maximum
```
Added value: +180
```
- addedInput schema / properties / position / properties / longitude / minimum
```
Added value: +-180
```
- addedInput schema / properties / scale / maximum
```
Added value: +100000
```
- addedInput schema / properties / scale / minimum
```
Added value: +0
```

Changed10 schema fields changedv1.139.14Apr 30, 2026

changedInput schema / properties / color / description

Previous value: -"新颜色（CSS 格式）"New value: +"New color (CSS format)"

changedInput schema / properties / entityId / description

Previous value: -"实体ID（addMarker/addPolyline 等返回的 entityId）"New value: +"Entity ID (returned by addMarker/addPolyline etc.)"

changedInput schema / properties / label / description

Previous value: -"新标注文本"New value: +"New label text"

changedInput schema / properties / position / description

Previous value: -"新位置坐标"New value: +"New position coordinates"

addedInput schema / properties / position / properties / height / description
```
Added value: +"高度（米）"
```
addedInput schema / properties / position / properties / latitude / description
```
Added value: +"纬度（-90 ~ 90）"
```
addedInput schema / properties / position / properties / longitude / description
```
Added value: +"经度（-180 ~ 180）"
```

changedInput schema / properties / scale / description

Previous value: -"新缩放比例"New value: +"New scale factor"

addedInput schema / properties / sessionId

Added value: +{
+  "description": "Target browser session ID for multi-browser routing (optional)",
+  "type": "string"
+}

changedInput schema / properties / show / description

Previous value: -"是否显示"New value: +"Whether to show"

First observedv1.139.4Mar 15, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the mutation and safety profile is covered. The description adds that data-source entities are supported, which is useful context, but says nothing about whether updates merge or replace existing properties, or about permission/session caveats. The return-shape sentence duplicates the existing output schema rather than adding behavioral insight.

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 sentences with the action and target front-loaded. The second sentence restating the return object is largely redundant given the output schema, which is the only wasted content.

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

Completeness5/5

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

With 8 parameters at 100% schema coverage, full annotations, and an output schema, the description only needs to convey intent and scope. It does that, naming the updateable facets and noting data-source entity support, so an agent has enough to call it correctly.

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%, so every parameter (including nested position coordinates and extrudedHeight) is already documented. The description only names the facets being changed and adds no syntax, format, or defaulting detail beyond the schema, so 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?

States a specific verb (update) and resource (entity) and enumerates the mutable facets: position, appearance, label, visibility, extrusion height. It does not explicitly contrast with siblings like updateLayerStyle or removeEntity, but the resource and field list make the target unambiguous.

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 about when to use this versus the many other mutation siblings (updateLayerStyle, removeEntity, addGeoJsonPrimitive). The phrase 'including data-source entities' implies scope but gives no prerequisites, exclusions, or alternative routing.

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