Position the SketchUp camera by defining eye, target, and up vectors, or frame a specific entity or the entire model for consistent views.
Set camera and optionally frame an entity or the whole model.
| Name | Required | Description | Default |
|---|---|---|---|
| up | No | ||
| eye | No | ||
| fov | No | ||
| path | No | ||
| unit | No | mm | |
| height | No | ||
| target | No | ||
| model_id | No | ||
| entity_id | No | ||
| active_path | No | ||
| perspective | No | ||
| zoom_extents | No |
Changes observed during successful MCP inspections.
v1.3.1Input schema / properties / active_pathAdded value: +{
+ "items": {
+ "exclusiveMinimum": 0,
+ "maximum": 9007199254740991,
+ "minimum": -9007199254740991,
+ "type": "integer"
+ },
+ "maxItems": 32,
+ "type": "array"
+}Input schema / properties / entity_id / $refAdded value: +"#/properties/active_path/items"Input schema / properties / entity_id / exclusiveMinimumRemoved value: -0Input schema / properties / entity_id / maximumRemoved value: -9007199254740991Input schema / properties / entity_id / minimumRemoved value: --9007199254740991Input schema / properties / entity_id / typeRemoved value: -"integer"Input schema / properties / heightAdded value: +{
+ "exclusiveMinimum": 0,
+ "type": "number"
+}Input schema / properties / model_idAdded value: +{
+ "minLength": 1,
+ "type": "string"
+}Input schema / properties / pathAdded value: +{
+ "items": {
+ "$ref": "#/properties/active_path/items"
+ },
+ "maxItems": 32,
+ "minItems": 1,
+ "type": "array"
+}v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false. The description adds only the optional framing behavior, with no information about persistence, return values, side effects, or what happens to existing camera state. It adds little beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence, but for a 12-parameter tool it is severely under-specified. Brevity is not serving the agent here because essential invocation context is missing.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 12 parameters, no required fields, no output schema, and no parameter descriptions, the one-sentence description is completely inadequate. An agent cannot determine how to set the camera or what the optional framing arguments should contain.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 12 parameters with 0% description coverage, so the description must compensate. It only vaguely references framing 'an entity or the whole model,' adding no meaning for eye, target, up, fov, path, height, unit, perspective, zoom_extents, active_path, or model_id.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb and resource: 'Set camera' with optional framing of an entity or the whole model. It distinguishes itself from camera_get by using 'Set,' but it does not explicitly name or differentiate against siblings. The scope is reasonably clear but not razor-sharp.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives such as camera_get or the various view/snapshot tools. 'Optionally frame an entity or the whole model' hints at a use case, but no conditions, prerequisites, or exclusions are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.