Skip to main content
Glama
prasadabhishek

photographi-mcp

photographi_analyze_folder

Batch analyzes all images in a folder with high concurrency, returning quality scores and judgments for each. Use pagination (limit/offset) to process up to 100 images per call, ideal for assessing overall shoot quality distribution.

Instructions

Batch analyzes all images in a folder with high concurrency (4-8 images at once). Returns quality scores and judgements for each image. Default limit is 100 images per call. Use 'limit' and 'offset' for pagination. If 'nextOffset' is in the response, call again with that offset. Perfect for understanding the overall quality distribution of a shoot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_pathYesAbsolute path to folder.
metricsNoSpecific metrics to calculate (sharpness, exposure, etc.). Defaults to all.
enable_subject_detectionNoUse AI for subject-aware analysis.
model_sizeNoYOLO model size.nano
limitNoBatch size for pagination.
offsetNoPagination offset. Increment this by 'limit' to see more results.
fast_modeNoDefaults to True (4-8x faster). Set to False for full-resolution 'Forensic Precision' mode (much slower on 40MP+ files).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: high concurrency (4-8 images), default limit of 100, pagination behavior, and performance trade-offs of fast_mode. It also implies read-only analysis, consistent with the tool's purpose.

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

Conciseness5/5

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

The description is concise, with three front-loaded sentences. Each sentence adds crucial information: the main function, pagination instructions, and use case. No filler or redundant content.

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

Completeness5/5

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

Given 7 parameters and an output schema, the description covers the essence: batch behavior, pagination, performance modes. It does not need to repeat schema details but provides sufficient context for an agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100% (baseline 3), the description adds value by explaining concurrency behavior not in schema, clarifying fast_mode's performance trade-off, and describing pagination with 'nextOffset'. This exceeds schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: batch analyzing all images in a folder. It specifies the resource (folder), action (analyze with high concurrency), and outcome (quality scores and judgements). This distinguishes it from sibling tools like photographi_analyze_photo, which handles single images.

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?

The description provides clear usage guidance: pagination with 'limit' and 'offset', and handling 'nextOffset'. It also recommends the tool for assessing overall quality distribution of a shoot. However, it does not explicitly state when to use alternatives, though this is implied by sibling names.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/prasadabhishek/photographi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server