Skip to main content
Glama

search_people

Search for people by full or partial name to locate individuals in your photo library. Returns matching people with ID, name, and photo count.

Instructions

Search for people by name (partial match). Use this when you know the person's name. For browsing all people, use list_people instead. Read-only.

Args:
    name: Full or partial name to match (case-insensitive).
    with_hidden: Include hidden people in results (default false).

Returns: JSON array of matching people with id, name, and photo count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
with_hiddenNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool registration for 'search_people' — decorated with @mcp.tool(), defines the tool interface (name, with_hidden params) and delegates to ImmichClient.search_people().
    @mcp.tool()
    async def search_people(ctx: Context, name: str, with_hidden: bool = False) -> str:
        """Search for people by name (partial match). Use this when you know the person's
        name. For browsing all people, use list_people instead. Read-only.
    
        Args:
            name: Full or partial name to match (case-insensitive).
            with_hidden: Include hidden people in results (default false).
    
        Returns: JSON array of matching people with id, name, and photo count.
        """
        result = await _client(ctx).search_people(name, with_hidden=with_hidden)
        return json.dumps(result, default=str)
  • Actual implementation: calls Immich REST API GET /search/person with query params 'name' and 'withHidden'.
    async def search_people(self, name: str, with_hidden: bool = False) -> list[dict]:
        """Search people by name."""
        params = {"name": name, "withHidden": str(with_hidden).lower()}
        return await self._request("GET", "/search/person", params=params)
Behavior4/5

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

Declares 'Read-only' and describes return fields. No annotations provided, so description carries full burden. Missing details on potential errors or pagination, but sufficient for a simple search tool.

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?

Five well-structured sentences, including an Args section. No wasted words.

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?

Covers purpose, usage, parameters, return format, and sibling differentiation. Output schema exists but description already mentions return fields. Complete for a simple tool with 2 parameters.

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

Parameters5/5

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

Schema coverage is 0%, but description adds meaning for both parameters: name is case-insensitive partial match, with_hidden includes hidden people and default false. This goes beyond schema titles.

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?

Description clearly states 'Search for people by name (partial match)' with a specific verb and resource. It distinguishes from sibling 'list_people' by noting that list_people is for browsing all.

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

Usage Guidelines5/5

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

Explicitly says 'Use this when you know the person's name. For browsing all people, use list_people instead.' Provides clear when-to-use and alternative.

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