Skip to main content
Glama

delete_contact

Remove a contact from the Keila newsletter system by specifying the contact ID to manage your subscriber list.

Instructions

Delete a contact.

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

Returns: Confirmation message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contact_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool registration and handler for `delete_contact`, which calls the KeilaClient to delete the contact.
    @mcp.tool()
    def delete_contact(contact_id: str) -> str:
        """
        Delete a contact.
    
        Args:
            contact_id: The contact ID (e.g. "c_12345").
    
        Returns:
            Confirmation message.
        """
        _client.delete_contact(contact_id)
        return f"Contact {contact_id} deleted."
  • The KeilaClient method that performs the actual API request to delete a contact.
    def delete_contact(self, contact_id: str, id_type: str | None = None) -> None:
        """Delete a contact."""
        params = {}
        if id_type:
            params["id_type"] = id_type
        resp = self.session.delete(f"{self.url}/api/v1/contacts/{contact_id}", params=params, headers=self._headers(), timeout=30)
        resp.raise_for_status()
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the return value ('Confirmation message'), but fails to mention destructive permanence, side effects on related campaigns, or required permissions. Slightly better than having no behavioral info, but significant gaps remain.

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 an efficient docstring structure (Args/Returns) with minimal verbosity. Every line conveys necessary information. Slightly terse given the behavioral risks of deletion, but no wasted words.

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 single-parameter tool with described output, but insufficient for a destructive operation lacking annotations. Missing critical context about whether deletion is permanent, cascades to campaigns, or error handling.

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 coverage is 0% (property lacks description), but the tool description compensates effectively by providing an example ID format ('c_12345') in the Args section, clarifying the expected string pattern.

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 action (Delete) and resource (contact) clearly. However, it is extremely minimal and lacks any scoping details (e.g., permanent deletion vs. archival) that would elevate it to a 5.

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 update_contact, nor prerequisites like verifying the contact exists. No mention of error conditions or irreversibility.

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