Skip to main content
Glama

Get a library capture

get_capture
Read-onlyIdempotent

One capture of the library and where it is used: every demo (id, title, guided or clickable, draft or live, whether it has unpublished changes) and each of its screens that links to the capture (id, name, the capture version it shows, whether it is still updating, how many steps or edits a replacement asked to look at, how many edits of its own the demo made on it). Use get_demo and get_screen for the screens themselves.

Requires: demos:read.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "captureId": "<captureId>"
    },
    "name": "get_capture"
  }
}

Input Schema

NameRequiredDescriptionDefault
captureIdYesA capture id from list_captures or get_demo (libraryCaptureId).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 those traits need no restating. The description adds a genuine extra: the required 'demos:read' scope, which is not captured in the annotations or schema. It does not mention error behavior for unknown or inaccessible capture ids.

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

Conciseness3/5

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

Purpose and scope are front-loaded, but the payload is delivered as one long nested parenthetical paragraph that is hard to parse at a glance. Several phrases, such as 'how many steps or edits a replacement asked to look at,' are dense enough to require re-reading.

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 carries the full burden of describing return values and does so field by field for both demos and linked screens, plus the auth prerequisite. Phrasing ambiguity in a few field glosses keeps it short of fully unambiguous.

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 schema description already explains that captureId comes from list_captures or get_demo (libraryCaptureId), including the pattern constraint. The description text adds nothing about the single parameter, which is the expected baseline when the schema does the work.

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 ('One capture of the library and where it is used') and enumerates the returned sub-objects. It explicitly distinguishes itself from get_demo and get_screen by scoping the screens to link summaries rather than the screens themselves.

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 context (retrieve a capture plus its usage across demos and screens) and a concrete exclusion: 'Use get_demo and get_screen for the screens themselves.' It does not contrast with list_captures or state when a bulk listing is preferable, so the routing is partial rather than exhaustive.

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.