whodb-cli

Official

Overview Schema Source Related Servers Discussions Admin

whodb_platform_app_views

Read-onlyIdempotent

List hosted app pages by ID or exact name so you can select a view for screenshot capture, with optional per-call workspace targeting.

Instructions

List pages in a hosted app by ID or exact name. Use a returned page with whodb_platform_app_screenshot. Accepts workspace {host, org, project} for per-call targeting without changing defaults.

Input Schema

Name	Required	Description
`app`	Yes	App ID or exact name in the selected project
`env`	No	published (default) or dev
`tab`	No	Optional visible tab or button label to open before capture
`page`	No	Optional page returned by whodb_platform_app_views
`trace`	No	Request an interaction trace from a compatible hosted app runtime
`width`	No	Viewport width, default 1440
`height`	No	Viewport height, default 900
`mobile`	No	Emulate a touch-enabled mobile browser; default viewport 390x844 unless width or height is set
`script`	No	Optional JavaScript expression or IIFE evaluated inside the app frame after actions
`tablet`	No	Emulate a touch-enabled tablet browser; default viewport 820x1180 unless width or height is set
`actions`	No	Ordered actions inside the app frame: click, fill, press, wait_for, or wait
`workspace`	No	Optional target for this call only. Omit to use the session default set by whodb_platform_session_use, then process/saved defaults. Discover targets with whodb_platform_hosts, whodb_platform_orgs and whodb_platform_projects.
`orientation`	No	Optional viewport orientation: portrait or landscape; rotates the device preset

Output Schema

Name	Required	Description
`app`	No
`env`	No
`error`	No
`scope`	No
`views`	No
`app_id`	No
`recovery`	No
`retryable`	No
`workspace`	No	Optional target for this call only. Omit to use the session default set by whodb_platform_session_use, then process/saved defaults. Discover targets with whodb_platform_hosts, whodb_platform_orgs and whodb_platform_projects.
`error_code`	No
`request_id`	No
`suggested_tools`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.136.0Oct 23, 2026

addedOutput schema / properties / error_code
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / recovery

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "LikelyCause": {
+      "type": "string"
+    },
+    "NextSteps": {
+      "items": {
+        "type": "string"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    }
+  },
+  "required": [
+    "LikelyCause",
+    "NextSteps"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / retryable
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / suggested_tools

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Addedv0.135.0Oct 15, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, and openWorld behavior. The description adds that workspace targeting is per-call and does not change defaults, which is useful, but it does not explain the many capture/interaction parameters visible in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three concise sentences with no filler. The core listing purpose is front-loaded, followed by the next-step tool reference and the workspace targeting detail.

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

Completeness3/5

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

The output schema, annotations, and full schema descriptions cover much of the burden. However, the description is very short relative to a 13-parameter schema that includes action, script, trace, viewport, and device-emulation options, leaving some ambiguity about whether this tool only lists pages or also captures/interacts with app views.

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 the schema already documents all parameters. The description only restates the app identifier and workspace object concepts, adding little beyond what the schema provides.

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 and resource: list pages in a hosted app by ID or exact name. It distinguishes itself from whodb_platform_app_screenshot by directing the agent to pass a returned page there, though it does not explicitly differentiate itself from the singular whodb_platform_app_view or whodb_platform_apps.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear next-step context: use a returned page with whodb_platform_app_screenshot. It also explains per-call workspace targeting without changing defaults. It stops short of explicit when-not-to-use guidance or naming all relevant alternatives.

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

Deploy Server