Skip to main content
Glama
Foto MCP Server
by thesven

foto_get_featured_photographers

Retrieves featured photographers and community ambassadors, returning bio summaries, follower statistics, and showcase links, with an optional limit up to 25.

Instructions

Discover community ambassador and featured creators on Foto with bio summaries, follower stats, and showcase links.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum featured photographers to return (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description does the behavioral work by disclosing that results carry bios, follower stats, and showcase links – useful context about what the read returns. It does not state whether authentication is required, how the featured list is ordered or curated, or whether results are paginated beyond the single limit cap.

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?

One sentence, front-loaded with the verb and resource, and the trailing clause on return contents earns its place because no output schema exists. There is no redundant restatement of the tool name.

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

Completeness4/5

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

For a zero-required-parameter read tool with no output schema, the description covers purpose and return shape adequately; the only meaningful gaps are the absence of auth/permission notes and of any ordering or curation caveat.

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 parameter (limit, max 25, default 10) is fully documented in the schema at 100% coverage, so the baseline applies. The description adds the notion of a bounded list of featured photographers but gives no guidance on choosing a limit or on ordering of the returned set.

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?

"Discover community ambassador and featured creators" names a specific verb and a specific curated resource, and the subsequent clause previews the returned content (bio summaries, follower stats, showcase links). This distinguishes it reasonably from feed tools, though it never explicitly contrasts with foto_get_photographer_profile or foto_find_photographers_by_tag, which also surface creators.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for surfacing a curated/featured roster rather than searching by tag or fetching one profile. There is no explicit when-to-use statement, no exclusion, and no mention of alternatives such as foto_find_photographers_by_tag for tag-driven discovery.

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