Skip to main content
Glama
TaylorChen

Multi-MCPs

by TaylorChen

search_photos

Find and retrieve photos from Unsplash by entering search terms, enabling visual content discovery for projects and presentations.

Instructions

Search Unsplash photos

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
per_pageNo

Implementation Reference

  • The handler function that executes the search_photos tool logic, validating inputs and calling the Unsplash client.
    async search_photos(args: Record<string, unknown>) {
      if (!cfg.unsplashAccessKey) throw new Error("UNSPLASH_ACCESS_KEY is not configured");
      const query = String(args.query || "");
      if (!query) throw new Error("query is required");
      const perPage = args.per_page ? Number(args.per_page) : undefined;
      return client.searchPhotos(query, perPage);
    },
  • Input schema for the search_photos tool, defining query as required string and optional per_page number.
    inputSchema: {
      type: "object",
      properties: { query: { type: "string" }, per_page: { type: "number" } },
      required: ["query"],
    },
  • Tool registration definition for search_photos within the Unsplash module's ToolRegistration.
    {
      name: "search_photos",
      description: "Search Unsplash photos",
      inputSchema: {
        type: "object",
        properties: { query: { type: "string" }, per_page: { type: "number" } },
        required: ["query"],
      },
    },
  • UnsplashClient.searchPhotos method, the core API call implementation for searching photos.
    searchPhotos(query: string, perPage?: number) {
      return this.request("/search/photos", { headers: this.headers(), query: { query, per_page: perPage ?? 10 } });
    }
  • Main registration invocation including the Unsplash tools (containing search_photos) in the aggregator.
    registerUnsplash(),
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but provides almost none. 'Search Unsplash photos' doesn't indicate whether this is a read-only operation, what authentication might be required, rate limits, pagination behavior, or what format the results take. The description fails to disclose any behavioral traits beyond the basic action.

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 maximally concise at just three words, with zero wasted language. It's appropriately sized for what it communicates, though what it communicates is insufficient. The structure is front-loaded with the essential action and resource.

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?

Given a search tool with 2 parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain what the tool returns, how results are structured, what authentication might be needed, or any usage constraints. For a search operation that presumably returns visual content, more context about result format and capabilities would be expected.

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

Parameters2/5

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

With 0% schema description coverage and 2 parameters (query and per_page), the description provides no information about what these parameters mean or how they should be used. It doesn't explain what types of queries are supported, what per_page controls, or any constraints on parameter values. The description fails to compensate for the complete lack of schema documentation.

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 clearly states the action ('Search') and resource ('Unsplash photos'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from sibling search tools like search_news, search_pages, search_places, search_repositories, or search_tracks - all of which follow the same 'Search [resource]' pattern without indicating what makes photo search unique.

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?

The description provides no guidance about when to use this tool versus alternatives. There's no mention of when this search should be preferred over get_random_photo or get_photo_details (both sibling tools), nor any context about what types of queries work best, what the tool returns, or any prerequisites for usage.

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/TaylorChen/muti-mcps'

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