set_viewportSet the center coordinates and zoom level of the editor viewport to focus on specific areas in Figma Slides.
Set editor viewport center and zoom
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": "set_viewport"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| zoom | No | ||
| center | No |
Changes observed during successful MCP inspections.
v0.1.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description must disclose behavioral traits, but it does not. It fails to mention side effects, reversibility, coordinate system, zoom units, or whether the change is temporary or persistent. The description only restates the core action without transparency.
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 sentence that is concise and front-loaded with the verb and resource. It is appropriately sized for the tool's simplicity, though it sacrifices detail for brevity.
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 the tool's complexity, the lack of annotations, output schema, and parameter documentation leaves the description incomplete. It does not tell the agent how to interpret the coordinate system or zoom scale, making it insufficient for reliable invocation.
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?
Schema description coverage is 0% for parameters, so the description must compensate. It only repeats the parameter names 'center' and 'zoom' without explaining what values they accept (e.g., zoom as a multiplier, center in pixels) or whether both are required. This adds minimal semantic value beyond the schema.
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 uses a specific verb 'Set' and clearly identifies the resource 'editor viewport' with what is being set ('center and zoom'). It is distinct from most siblings but does not explicitly distinguish itself from 'zoom_to_fit', which also affects the viewport, so it loses a point for lack of differentiation.
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?
No usage guidance is provided beyond the basic action. There is no mention of when to use this tool versus a sibling like 'zoom_to_fit', nor any prerequisites or context about how it fits into a workflow.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.