Skip to main content
Glama

get_person_thumbnail

Retrieve a face crop thumbnail for a person to visually identify them before merging or renaming. Returns base64 image data.

Instructions

Get a base64-encoded face crop thumbnail for a person. Use this to visually identify a person before merging or renaming. Read-only.

Args:
    person_id: The person's UUID.

Returns: JSON with 'data' (base64 string of face crop) and 'type' (MIME type).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
person_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool registration for get_person_thumbnail via @mcp.tool() decorator. Calls the client method and returns JSON.
    @mcp.tool()
    async def get_person_thumbnail(ctx: Context, person_id: str) -> str:
        """Get a base64-encoded face crop thumbnail for a person. Use this to visually
        identify a person before merging or renaming. Read-only.
    
        Args:
            person_id: The person's UUID.
    
        Returns: JSON with 'data' (base64 string of face crop) and 'type' (MIME type).
        """
        result = await _client(ctx).get_person_thumbnail(person_id)
        return json.dumps(result)
  • Input schema: person_id (string) and output: JSON with 'data' (base64 string) and 'type' (MIME type).
    """Get a base64-encoded face crop thumbnail for a person. Use this to visually
    identify a person before merging or renaming. Read-only.
    
    Args:
        person_id: The person's UUID.
    
    Returns: JSON with 'data' (base64 string of face crop) and 'type' (MIME type).
    """
  • Core handler that makes the actual HTTP GET request to /api/people/{person_id}/thumbnail, returns base64-encoded image data.
    async def get_person_thumbnail(self, person_id: str) -> dict:
        """Get a base64-encoded face thumbnail for a person."""
        url = f"{self.base_url}/api/people/{person_id}/thumbnail"
        async with httpx.AsyncClient(timeout=30.0) as client:
            response = await client.get(url, headers=self._headers)
            response.raise_for_status()
            content_type = response.headers.get("content-type", "image/jpeg")
            b64 = base64.b64encode(response.content).decode("ascii")
            return {"data": b64, "type": content_type}
Behavior4/5

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

No annotations provided, but description declares 'Read-only' and specifies return format (JSON with 'data' and 'type'). Adequate disclosure for a simple read operation.

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?

Two paragraphs plus parameter description, each sentence adds value. No fluff, well structured.

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

Completeness5/5

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

Simple operation with one parameter; description covers purpose, usage context, parameter, and output format completely.

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 description coverage is 0%, but description adds 'The person's UUID' to the parameter, clarifying its purpose beyond type/title.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource: 'Get a base64-encoded face crop thumbnail for a person.' Clear distinction from siblings like get_person or merge_people.

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

Usage Guidelines4/5

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

Explicit when-to-use: 'Use this to visually identify a person before merging or renaming.' Lacks explicit when-not-to or alternatives, but context is sufficient.

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/drolosoft/immich-photo-manager'

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