PhotoForge MCP Server

list_generations

Retrieve recent AI-generated fashion photography and video assets from the studio using limit and offset for pagination.

Instructions

Retrieve recent AI generations created in the studio.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Number of generations to return.
`offset`	No	Pagination offset.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 24, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden, yet it never states that this is a read-only operation, whether results are scoped to the calling user/workspace, what 'recent' means, or what the response contains. The implicit ordering by recency is the only behavioral detail, and even that is only suggested.

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 front-loaded sentence with no filler or redundancy. It is efficient, though the brevity edges into under-specification rather than true crispness.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a list tool with no annotations and no output schema, the description omits the return shape, default ordering, recency window, and result scoping. An agent can guess limit/offset semantics from the schema, but little else is established.

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%, so both limit and offset are already documented; the description only contributes the notion of recency. Baseline 3 applies since the schema does the semantic heavy lifting and the description adds no syntax or ordering caveats.

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 ('Retrieve') and resource ('AI generations'), scoped to 'recent' ones in the studio. It does not name or distinguish itself from siblings such as list_photo_packs or list_identities, so the agent must infer the boundary from the resource noun alone.

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?

No guidance on when to use this versus other listing or generation tools, no prerequisites, and no exclusions. The word 'recent' loosely hints at a time window but never defines it or points to any alternative for older or filtered results.

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