Skip to main content
Glama

list_contacts

Retrieve and display all contacts from the Keila newsletter system with pagination support. View contact details including email, name, status, and timestamps.

Instructions

List all contacts in Keila with pagination.

Args: page: Page number for pagination (optional).

Returns: A dict with 'data' (list of contacts) and 'meta' (pagination info). Each contact has id, email, first_name, last_name, status, data, and timestamps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo

Implementation Reference

  • MCP tool handler for listing contacts, which delegates the call to the KeilaClient.
    @mcp.tool()
    def list_contacts(page: int | None = None) -> dict:
        """
        List all contacts in Keila with pagination.
    
        Args:
            page: Page number for pagination (optional).
    
        Returns:
            A dict with 'data' (list of contacts) and 'meta' (pagination info).
            Each contact has id, email, first_name, last_name, status, data, and timestamps.
        """
        return _client.list_contacts(page=page)
  • The actual API client implementation for listing contacts via HTTP request.
    def list_contacts(self, page: int | None = None, filter: dict | None = None) -> dict:
        """List contacts with optional pagination and filtering."""
        params = {}
        if page is not None:
            params["paginate[page]"] = page
        if filter:
            for key, val in filter.items():
                params[f"filter[{key}]"] = val
        resp = self.session.get(f"{self.url}/api/v1/contacts", params=params, headers=self._headers(), timeout=30)
        resp.raise_for_status()
        return resp.json()
Behavior3/5

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

No annotations provided, so description carries full burden. Compensates partially by detailing return structure (dict with 'data' and 'meta') and contact fields. However, omits critical behavioral details: page size limits, whether results are sorted, read-only safety guarantees, and rate limiting.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Uses structured Args/Returns format that efficiently organizes information. Front-loads the primary purpose. Slightly verbose construction but every sentence serves a purpose given the lack of output schema.

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?

Adequate for a simple 1-parameter read operation. Documents the return structure since no output schema exists. Missing: pagination size limits, sorting behavior, and maximum page bounds necessary for effective API consumption.

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 has 0% description coverage (page parameter lacks description field). Tool description successfully compensates by explaining 'page' is for 'pagination' and marking it 'optional', though could further clarify default behavior (e.g., first page when omitted).

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?

States specific verb ('List') and resource ('contacts') with scope ('all... with pagination'). However, fails to differentiate from sibling 'get_contact' (presumably singular retrieval) or clarify when to use full list vs. individual fetch.

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?

Provides no guidance on when to use this versus 'get_contact' for individual lookups, nor prerequisites like authentication requirements. No mention of when pagination is necessary or recommended.

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/gwbischof/keila-mcp'

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