Skip to main content
Glama
TaylorChen

Multi-MCPs

by TaylorChen

get_photo_details

Retrieve detailed information about a specific photo using its unique identifier within the Multi-MCPs server's aggregated API services.

Instructions

Get photo details by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
photo_idYes

Implementation Reference

  • The main handler function for the 'get_photo_details' tool. It checks for the required Unsplash access key configuration, extracts the photo_id from args, validates it, and delegates to the UnsplashClient's getPhotoDetails method.
    async get_photo_details(args: Record<string, unknown>) {
      if (!cfg.unsplashAccessKey) throw new Error("UNSPLASH_ACCESS_KEY is not configured");
      const photoId = String(args.photo_id || "");
      if (!photoId) throw new Error("photo_id is required");
      return client.getPhotoDetails(photoId);
    },
  • Input schema definition for the 'get_photo_details' tool, specifying that 'photo_id' is a required string.
    inputSchema: {
      type: "object",
      properties: { photo_id: { type: "string" } },
      required: ["photo_id"],
    },
  • Tool registration entry for 'get_photo_details' in the tools array returned by registerUnsplash, including name, description, and input schema.
    {
      name: "get_photo_details",
      description: "Get photo details by ID",
      inputSchema: {
        type: "object",
        properties: { photo_id: { type: "string" } },
        required: ["photo_id"],
      },
    },
  • Helper method in the UnsplashClient class that performs the actual API request to retrieve photo details by ID from the Unsplash API.
    getPhotoDetails(photoId: string) {
      return this.request(`/photos/${photoId}`, { headers: this.headers() });
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic operation without behavioral details. It doesn't disclose if this is a read-only operation, requires authentication, has rate limits, or what the response format might be (e.g., JSON with fields). For a tool with zero annotation coverage, this is a significant gap, scoring 2 for minimal disclosure.

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 'Get photo details by ID' is a single, front-loaded sentence with zero waste—every word earns its place by specifying the action, resource, and key parameter. It's appropriately sized for a simple retrieval tool, making it highly concise and well-structured.

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 no annotations, no output schema, and low schema coverage (0%), the description is incomplete. It doesn't explain what 'details' include, potential errors (e.g., invalid ID), or return values, which are critical for a retrieval tool. The simplicity of the tool (1 parameter) mitigates this slightly, but overall, it lacks sufficient context for effective use.

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 0%, so the description must compensate. It mentions 'by ID', which clarifies that 'photo_id' is an identifier for a photo, adding meaning beyond the schema's generic string type. However, it doesn't specify ID format (e.g., numeric, UUID) or examples, so it partially compensates but not fully, aligning with the baseline 3 for moderate value addition.

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 'Get photo details by ID' clearly states the verb 'Get' and resource 'photo details', specifying it operates on a photo identified by ID. It distinguishes from siblings like 'search_photos' (which searches rather than retrieves by ID) and 'get_random_photo' (which retrieves random photos). However, it doesn't specify what 'details' include (e.g., metadata, dimensions), keeping it at 4 rather than 5.

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?

The description implies usage when you have a specific photo ID to retrieve details, contrasting with 'search_photos' for broader queries and 'get_random_photo' for random selection. However, it lacks explicit guidance on when not to use it (e.g., if you need multiple photos) or prerequisites (e.g., valid ID format), leaving it at an implied level.

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