Skip to main content
Glama

Review Recording

review_recording
Read-onlyIdempotent

Open a recording for review; in MCP Apps clients, provide an inline player to scrub, trim, redact, and export, otherwise show the video’s details.

Instructions

Open a recording for a person to review: in MCP Apps clients an inline player to scrub, trim, and redact, then export; elsewhere just the video's details.

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

Input Schema

NameRequiredDescriptionDefault
inputNoPath to the video.
sessionIdNoOr the session id of a stopped recording.

Output Schema

NameRequiredDescriptionDefault
fpsYes
inputYes
widthYes
heightYes
hasAudioYes
durationSecYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.47.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "durationSec": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "fps": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "hasAudio": {
      +      "type": "boolean"
      +    },
      +    "height": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "input": {
      +      "type": "string"
      +    },
      +    "width": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "input",
      +    "durationSec",
      +    "width",
      +    "height",
      +    "fps",
      +    "hasAudio"
      +  ],
      +  "type": "object"
      +}
  2. Addedv0.39.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for the extra context it adds: behavior is client-dependent, with an inline scrub/trim/redact/export player in MCP Apps clients and a passive details view elsewhere. The tension between 'trim and redact' and readOnlyHint is best read as UI capabilities rather than this call mutating anything, but it is left for the agent to resolve.

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?

A single sentence, front-loaded with the action and then the two client modes, with no filler. The parenthetical clause ('in MCP Apps clients an inline player to scrub...') is slightly compressed but still parseable.

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 an output schema and annotations available, the description only needs the mode-dependent behavior delta, which it delivers. The main omission is the mutually exclusive input/sessionId requirement, which an agent must get from the schema.

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 both properties are documented, including the either/or between a file path and a stopped session id. The description adds nothing about parameters and does not even restate that exactly one of input/sessionId must be supplied, so 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+resource ('open a recording for a person to review') and clarifies the deliverable in each context (interactive player vs. plain video details). It implicitly separates itself from pure-data siblings like get_media_info or get_session, though it never names them.

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: 'for a person to review' suggests human-in-the-loop work versus programmatic extraction. It never says when to pick this over get_media_info, get_session, or screenshot, and gives no prerequisites, so the agent must infer the routing itself.

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