list_grabsBrowse your team's recent screenshots (newest first).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Rows to return (default 20) | |
| status | No | Filter by status |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | ||
| has_more | Yes |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": {},
+ "properties": {
+ "data": {
+ "items": {
+ "additionalProperties": {},
+ "properties": {
+ "bytes": {
+ "anyOf": [
+ {
+ "maximum": 9007199254740991,
+ "minimum": 0,
+ "type": "integer"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "Image size in bytes."
+ },
+ "created_at": {
+ "description": "ISO 8601 creation time.",
+ "type": "string"
+ },
+ "error_message": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "Why a failed grab failed."
+ },
+ "execution_ms": {
+ "anyOf": [
+ {
+ "maximum": 9007199254740991,
+ "minimum": 0,
+ "type": "integer"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "Render time in milliseconds."
+ },
+ "format": {
+ "anyOf": [
+ {
+ "enum": [
+ "png",
+ "jpeg",
+ "webp"
+ ],
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "Image format."
+ },
+ "height": {
+ "anyOf": [
+ {
+ "maximum": 9007199254740991,
+ "minimum": 0,
+ "type": "integer"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "Viewport height in pixels (3240 in the response for full_page captures)."
+ },
+ "id": {
+ "description": "Grab id.",
+ "type": "string"
+ },
+ "image_url": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "Hosted image URL once status is done (relative for sk_test_ placeholders)."
+ },
+ "status": {
+ "description": "Lifecycle state. Only done grabs have an image_url.",
+ "enum": [
+ "pending",
+ "processing",
+ "done",
+ "failed"
+ ],
+ "type": "string"
+ },
+ "target_url": {
+ "description": "The captured URL.",
+ "type": "string"
+ },
+ "width": {
+ "anyOf": [
+ {
+ "maximum": 9007199254740991,
+ "minimum": 0,
+ "type": "integer"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "Viewport width in pixels."
+ }
+ },
+ "required": [
+ "id",
+ "status",
+ "created_at"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "has_more": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "data",
+ "has_more"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the useful ordering trait (newest first) but says nothing about pagination or result volume, so it adds modest value 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?
A single sentence with zero filler, front-loading the verb and resource and appending the ordering constraint where it belongs.
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?
An output schema exists, so return values need no explanation, and the read-only annotations cover safety. For a simple two-parameter list tool the description is nearly complete, with only pagination behavior left implicit.
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 100%: limit has a documented default (20) and status has a documented enum, so the schema carries the parameter burden. The description adds no filtering or limit semantics of its own, making the baseline 3 appropriate.
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?
States a specific verb (browse) and resource (team's recent screenshots, i.e. grabs) plus the sort order (newest first). It does not explicitly distinguish itself from the sibling get_grab, but the plural/listing framing makes the distinction inferable.
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?
The phrase 'your team's recent' implies the listing use case, but there is no explicit when-to-use guidance and no mention of when to prefer get_grab for a single item. Usage is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.