Skip to main content
Glama
Sign In

Playbook

by com.playbook
OverviewDiscussionsAdmin

List hosted apps

list_apps
Read-only

List the hosted apps of a workspace: small web apps, each showing one board, that were deployed with deploy_app. Returns each app's slug, name, url, the board_token of the board it shows, access (who may open it: public, password or members), enabled and head_version_number. An app with enabled: false was switched off: its address answers 404 and no tool here switches it back on. head_version_number is the live version: Playbook keeps the files of an app's last 50 deploys, which get_app_source reads, edit_app_source changes, list_app_versions lists and revert_app puts back live.

Tool call template

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": "list_apps"
  }
}

Input Schema

NameRequiredDescriptionDefault
organizationNoWorkspace slug, as returned by list_organizations. Omit it when the account has a single workspace — it is then resolved from your token. Pass it only when the account has several, or when you mean a workspace other than the obvious one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the read-only, non-destructive profile, and the description adds substantial behavior beyond that: disabled apps return 404 and cannot be re-enabled by any tool here, and Playbook retains only the last 50 deploys' files. It also names the access levels (public/password/members) and clarifies that head_version_number is the live version. This is exactly the operational context annotations cannot carry.

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

Conciseness4/5

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

Front-loaded with purpose, then return fields, then behavioral caveats, then related tools — a sensible order. The final sentence is dense, chaining four sibling tool names and the 50-deploy retention rule together, but no sentence is pure filler.

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

Completeness5/5

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

With no output schema, the description carries the full burden of describing return values and does so field by field, including the meaning of `enabled` and `head_version_number`. For a simple one-optional-parameter listing tool, nothing an agent needs is missing.

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 coverage is 100% and the single `organization` parameter is fully documented in the schema, including when to omit it. The description adds no parameter-level meaning of its own, so the baseline of 3 for schema-documented parameters applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List the hosted apps of a workspace') and then defines the resource precisely: small web apps, each showing one board, deployed with deploy_app. That definition, plus the pointer to deploy_app, cleanly separates it from sibling listing tools such as list_app_versions and list_boards.

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?

Usage context is clear — this is the entry point for discovering hosted apps, and the description routes the agent onward: deploy_app creates them, get_app_source reads files, edit_app_source changes them, list_app_versions lists versions, revert_app restores one. It also flags that nothing here re-enables a disabled app, which steers the agent away from a wrong assumption. It stops short of explicitly saying when not to call it versus those siblings.

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

All Playbook toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources