Skip to main content
Glama

get_albums

Retrieve photo albums from a specific band using its unique identifier. This tool enables users to access and view band photo collections through the Band API integration.

Instructions

Get photo albums from a specific band in BAND.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
band_keyYesband ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
result_codeYesResult code
result_dataYesResult data

Implementation Reference

  • The main handler function for the get_albums tool. It fetches photo albums from the BAND API using the provided band_key and returns the JSON response as text content.
    export async function handleToolCall(band_key: string) {
      const albumsData = await bandApiClient.get<AlbumsResponse>(
        "/v2/band/albums",
        { band_key }
      );
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(albumsData, null, 2),
          },
        ],
      };
    }
  • Defines the tool schema including input (band_key) and detailed output schema for the albums response structure.
    export const ToolDefinition: Tool = {
      name: "get_albums",
      description: "Get photo albums from a specific band in BAND.",
      inputSchema: {
        type: "object",
        properties: {
          band_key: {
            type: "string",
            title: "Band ID",
            description: "band ID",
          },
        },
        required: ["band_key"],
      },
      outputSchema: {
        type: "object",
        properties: {
          result_code: {
            type: "number",
            description: "Result code",
          },
          result_data: {
            type: "object",
            description: "Result data",
            properties: {
              paging: {
                type: "object",
                description: "Paging information",
              },
              items: {
                type: "array",
                description: "List of photo albums",
                items: {
                  type: "object",
                  properties: {
                    photo_album_key: {
                      type: "string",
                      description: "photo album identifier",
                    },
                    name: {
                      type: "string",
                      description: "album name",
                    },
                    photo_count: {
                      type: "number",
                      description: "number of photos in album",
                    },
                    cover_photo: {
                      type: "object",
                      description: "album cover photo information",
                    },
                    created_at: {
                      type: "number",
                      description: "album created time",
                    },
                  },
                },
              },
            },
          },
        },
        required: ["result_code", "result_data"],
      },
    };
  • src/tools.ts:60-61 (registration)
    Registers the get_albums tool in the main dispatcher switch statement, calling the albums module's handler.
    case "get_albums":
      return albums.handleToolCall(a.band_key as string);
  • src/tools.ts:22-22 (registration)
    Includes the get_albums ToolDefinition in the exported bandTools array for tool listing and discovery.
    albums.ToolDefinition,
  • Re-exports ToolDefinition and handleToolCall from tool.ts for use in the main tools.ts module.
    import {ToolDefinition, handleToolCall} from "./tool.js";
    
    const albums = {ToolDefinition, handleToolCall}
    
    export default albums;
Behavior2/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. It states the tool 'Get photo albums' but doesn't clarify whether this is a read-only operation, if it requires authentication, what the output format looks like, or any rate limits. The description lacks essential behavioral context for a tool with no annotation coverage.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, with zero wasted information.

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?

Given the tool's simplicity (1 parameter, 100% schema coverage, and an output schema exists), the description is minimally adequate. However, with no annotations and no guidance on usage or behavior, it leaves gaps in understanding how to effectively invoke the tool in context with siblings.

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 input schema has 100% description coverage, with the parameter 'band_key' clearly documented as 'band ID'. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate.

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 ('Get photo albums') and the target resource ('from a specific band in BAND'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate this tool from sibling tools like 'get_photos' or 'get_bands', which might retrieve related but different resources.

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 on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_photos' (which might retrieve individual photos) or 'get_bands' (which might retrieve band information), nor does it specify prerequisites or exclusions 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/kanghouchao/band-mcp-server'

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