Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

List recording designs

list_recording_designs
Read-onlyIdempotent

Lists available clip, video, and audio recording designs, including which design new recordings use by default; read-only.

Instructions

The designs (templates) available for clips, for video and for audio recordings, and which one new recordings use by default. Reads only.

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

Input Schema

NameRequiredDescriptionDefault
account_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so 'Reads only' is largely redundant. The description does add real context beyond the annotations by stating that the listing includes which design new recordings use by default, but it says nothing about pagination, ordering, or what happens when no designs exist.

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 compact sentence with no filler, and the content is front-loaded. The phrasing 'for video and for audio recordings' is slightly clunky but costs little.

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?

With no output schema, the description does well to name the payload (available designs plus the default), which is the key return-value fact. It is still thin for a listing tool: no ordering, no indication of the shape of each design entry, and no note that account_id only matters in multi-account setups.

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 reported as 0%, so strictly the description should compensate for the single account_id parameter, and it does not. In practice the schema carries a usable inline description of account_id, so the practical gap is small and a 3 is fair.

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?

The description names the specific resource (recording design templates) and scopes it to clips, video and audio, plus notes that it reports the default. That is clearly distinct from mutation siblings like set_default_recording_design or change_clip_design, though the verb is implied by the name rather than stated.

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

Usage Guidelines2/5

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

'Reads only' is a safety statement, not usage guidance. Nothing says when an agent should call this versus set_default_recording_design (to change the default) or change_clip_design (to alter a clip), and no prerequisite for discovering valid design ids is given.

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

Deploy Server

Other Tools