Skip to main content
Glama

List library captures

list_captures
Read-onlyIdempotent

The workspace’s capture library: captured screens (a screenshot and, with HTML capture, the page) that screens in many demos link to, so one edit or replacement updates every demo. Each has an id, name, page title and address (without query or ids), size, whether it has an HTML page, its version and how many demos and screens use it. Most recently changed first. Linked screens show libraryCaptureId in get_demo.

Requires: demos:read.

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_captures"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNohtml: captures with an HTML page; image: screenshot only.
queryNoOnly captures whose name, page title or address contains this (case-insensitive).
usageNoused: linked from at least one demo; unused: from none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine context beyond that: default ordering (most recently changed first), the set of fields returned per item, the propagation semantics of the library, and an explicit permission requirement ('Requires: demos:read').

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?

The concept is front-loaded and the field inventory is packed into one sentence rather than a bullet list, which keeps it compact. The parenthetical about HTML capture and the propagation clause both earn their place, though the second paragraph's permission line is a slightly abrupt tack-on.

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

Completeness4/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 compensates by enumerating returned fields and stating sort order, and it covers the access prerequisite. Since no pagination or limit parameters exist, omitting result-size behavior is a minor gap rather than a blocker for a 3-param read tool.

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% and both enums carry inline descriptions, so the parameters are already well documented. The description adds no filter-specific meaning beyond what the schema says; its only parameter-adjacent note is that linked screens expose `libraryCaptureId` in get_demo, which is about return data, not inputs. Baseline 3 applies.

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 ('The workspace's capture library') and explains the domain concept well — shared screens that demos link to, so edits propagate. It also cross-references get_demo's `libraryCaptureId` field, which anchors the resource in the wider tool set. It stops short of naming a single-capture sibling like get_capture as the alternative for one item.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the enumeration endpoint for captures and that the kind/usage/query filters narrow results. There is no explicit 'use this when…' or 'use get_capture instead when…' routing, and no exclusions stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.