zen_set_zoom
Set a browser tab's zoom factor to a value from 0.3 to 5.0, controlling page display size.
Instructions
Set zoom factor. 0.3 to 5.0 typical; 1.0 = 100%.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| factor | Yes | ||
| tab_id | No |
Set a browser tab's zoom factor to a value from 0.3 to 5.0, controlling page display size.
Set zoom factor. 0.3 to 5.0 typical; 1.0 = 100%.
| Name | Required | Description | Default |
|---|---|---|---|
| factor | Yes | ||
| tab_id | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Discloses typical range and meaning of 1.0, but does not explain effects of tab_id (null vs. integer), persistence, or scope. Minimal behavioral context.
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?
Single sentence with all essential information. No redundant words. Efficient and front-loaded.
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?
Adequate for a simple tool with one required parameter, but lacks detail on tab_id behavior and scope. Given no output schema, could be more complete.
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 coverage is 0% with no parameter descriptions. Description adds meaning for 'factor' (range and default meaning) but does not explain 'tab_id' at all. Partial improvement over schema alone.
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?
Clearly states the action 'Set zoom factor' and the resource. Distinguishes from sibling 'zen_get_zoom' but not from other set tools. Lacks explicit 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 guidance on when to use or alternatives. Only implies usage for changing zoom, but no context or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/JayQuan-McCleary/ZenLink-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server