Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

List recordings

list_recordings
Read-onlyIdempotent

Retrieve recent account recordings and their generated clips, including clip details and Scheduling post IDs and statuses. Read-only access supports reviewing content and posting progress.

Instructions

The account's recent recordings with status and the clips each produced: clip id, title, post text, video link, design, and the id and status of the clip's post in Scheduling. 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_recordings"
  }
}

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, destructiveHint=false and openWorldHint=false, so 'Reads only' merely repeats structured data and earns no credit. What the description does add is the returned content: recording status and the fields of each produced clip, including the linked Scheduling post id and status, which is real value in the absence of an output schema. It still omits how 'recent' is bounded and whether results are paginated or limited.

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?

One front-loaded sentence naming the resource and then enumerating the returned clip fields, plus a short safety note. The field enumeration is dense but justified because no output schema exists; little is wasted.

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?

For a read-only, single-optional-param tool this covers return content adequately, but it leaves gaps an agent needs: what window 'recent' covers, whether there is a result cap or pagination, and how it relates to the Recording-related sibling tools.

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?

The single optional account_id is already documented in the schema with a clear explanation of when to include it. The description only implies account scoping via 'The account's' and adds no meaning about the parameter, so the schema carries the burden and a 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?

The description identifies the resource (the account's recent recordings), its scope (recent), and the payload shape (recordings with status plus the clips each produced). It never uses the verb 'list' explicitly and doesn't differentiate from siblings such as list_posts or list_recording_designs, but an agent can still tell what it returns.

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?

There is no statement of when to call this versus list_posts, list_recording_designs, or full_list, and no prerequisites or exclusions. Usage is only implied by the word 'recent recordings'.

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