Skip to main content
Glama
Foto MCP Server
by thesven

foto_get_explore_feed

Retrieve a curated explore feed of recent public works across major photography genres, optionally filtered by tags and limited in size.

Instructions

Retrieve a rich curated explore feed of recent public works across major photographic genres (Street, Landscape, Portrait, Analog, Fine Art, Architecture).

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

Input Schema

NameRequiredDescriptionDefault
tagsNoOptional subset of curated tags to explore
limitNoMaximum explore posts to return (default: 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. 'Retrieve' and 'public works' imply a non-destructive read over publicly visible content, and the genre curation and recency are useful behavioral facts, but nothing is said about ordering, pagination, or authentication requirements. It is adequate for a read-only feed but leaves notable gaps.

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 redundant sentences; the genre list is informative rather than padding. The adjective 'rich' is mild filler that could be dropped, but the sentence is otherwise efficient.

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 simple two-optional-parameter read tool with no output schema and no annotations, the description covers what the tool returns at a high level. It does not describe the shape of returned posts or pagination behavior, which an agent may need to chain calls 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?

Schema coverage is 100%, so the parameters are already documented, yet the description still adds meaning: it clarifies that 'tags' draws from a curated tag set and that results are recent public works, framing what the limit applies to. Given the schema already covers defaults and bounds, this is slightly above the baseline.

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 uses a specific verb ('Retrieve') and a well-defined resource ('curated explore feed of recent public works'), and it enumerates the genres covered, which tells an agent what content to expect. It stops short of explicitly distinguishing this from the sibling foto_get_home_feed or foto_browse_tag, leaving the explore-vs-home distinction implicit.

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 prefer this over foto_get_home_feed (personalized feed) or foto_browse_tag (tag-specific browsing), and no exclusions or prerequisites. The word 'explore' hints at discovery browsing, but the agent must infer that from names alone.

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