Skip to main content
Glama

get_contact

Retrieve a specific contact's details from the Keila newsletter platform by providing their unique contact ID.

Instructions

Fetch a single contact by ID.

Args: contact_id: The contact ID (e.g. "c_12345").

Returns: A dict with contact details: id, email, first_name, last_name, status, data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contact_idYes

Implementation Reference

  • The MCP tool handler function 'get_contact' registered with @mcp.tool() which calls the underlying KeilaClient.get_contact method.
    @mcp.tool()
    def get_contact(contact_id: str) -> dict:
        """
        Fetch a single contact by ID.
    
        Args:
            contact_id: The contact ID (e.g. "c_12345").
    
        Returns:
            A dict with contact details: id, email, first_name, last_name, status, data.
        """
        return _client.get_contact(contact_id)
  • client.py:49-56 (handler)
    The implementation logic of the KeilaClient.get_contact method which performs the HTTP GET request to the Keila API.
    def get_contact(self, contact_id: str, id_type: str | None = None) -> dict:
        """Fetch a single contact by ID."""
        params = {}
        if id_type:
            params["id_type"] = id_type
        resp = self.session.get(f"{self.url}/api/v1/contacts/{contact_id}", params=params, headers=self._headers(), timeout=30)
        resp.raise_for_status()
        return resp.json()
Behavior4/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 successfully documents the return structure (dict with id, email, first_name, last_name, status, data), which compensates for the missing output schema. However, it lacks details on error behavior (e.g., contact not found) or authorization requirements.

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?

The docstring-style format with explicit Args and Returns sections is structured and scannable. While slightly more verbose than a single paragraph, every section earns its place by providing essential information not present in the structured schema fields.

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

Completeness4/5

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

Given this is a simple read operation with one parameter and no output schema, the description is adequately complete. It documents the input parameter and output structure sufficiently. A minor gap is the absence of error handling documentation, but this is acceptable for a basic getter tool.

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 description coverage is 0%, meaning the JSON schema property has no description. The description fully compensates by documenting the contact_id parameter with both semantics ('The contact ID') and a clear example value ('c_12345'), providing everything needed to invoke the tool correctly.

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?

The description 'Fetch a single contact by ID' provides a specific verb (fetch), resource (contact), and scope (single by ID). It clearly distinguishes this from the sibling list_contacts tool which handles multiple records.

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 phrase 'single contact by ID' implies usage for retrieving specific known records versus listing/filtering, offering implicit differentiation from list_contacts. However, there is no explicit guidance on when to use this versus create_contact or update_contact, or prerequisites like needing a valid ID.

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