Clay
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLAY_API_KEY | Yes | Your Clay API key. You can generate this by logging into Clay at https://web.clay.earth/settings/api-keys |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchContactsA | Search for contacts and return matching people. Use for questions about specific contacts or "who" questions (e.g. "Who did I meet most?" or "who works as an engineer?"). Returns actual contact records for queries needing specific people. |
| searchInteractionsA | Search for interactions and return matching interactions. Use for questions about specific interactions, "who" questions (e.g. "Who did I meet most?"), finding best friends based on relevance score, or finding recently added/created contacts. Returns actual contact records for queries needing specific interactions. |
| aggregateContactsA | Get numerical statistics and counts ONLY. Returns numbers and percentages, never specific contacts. For counting questions like "how many work at Google?" or "what % are engineers?". Use search endpoint instead for any "who" questions or to get actual contact details. |
| getContactB | Get details for a contact by id, including emails, social links, phone numbers, and notes. |
| createContactA | Create a new contact record in Clay. This endpoint should only be used when you need to create a completely new contact, not for adding contacts to groups. |
| createNoteA | Create a note for a contact. Only use this when the user explicitly asks to create, add, or save a note. |
| getGroupsC | Get all groups or lists for the user. |
| createGroupB | Create a group or list for the user. If a group with the same name already exists, it will not create a duplicate unless explicitly requested to ignore the check. |
| updateGroupA | Update a group or list. Use this to update the group title and/or modify its members. When adding or removing contacts, provide ALL contact IDs to add/remove in a single call - do not make multiple calls for individual contacts. |
| getNotesA | Use ONLY when the user explicitly mentions "note" or "notes" to retrieve notes between two dates (e.g. "what notes from last week?"). Returns notes by creation date only - does NOT search note content or filter by other criteria. NEVER use this tool for finding contacts or any other purpose besides retrieving notes. This tool is strictly prohibited from being used unless "note" or "notes" are explicitly mentioned in the query. |
| getEventsA | Use this tool ONLY to fetch meetings/events in a date range (e.g. "what meetings next week?", "show calendar for tomorrow"). DO NOT use for counting meetings, analyzing patterns, or finding frequent participants. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools have distinct purposes, but there is notable overlap between searchContacts and searchInteractions, as both can return contact records for 'who' questions, which could cause confusion. Additionally, aggregateContacts and getEvents have restrictive descriptions that might lead to misselection if an agent misinterprets the query.
Tool names follow a consistent verb_noun pattern throughout, such as createContact, getContact, searchContacts, and updateGroup. All names use camelCase uniformly, making them predictable and easy to understand.
With 11 tools, the count is well-scoped for a contact management server, covering core operations like CRUD for contacts, groups, notes, and events, as well as search and aggregation functions. Each tool appears to serve a specific purpose without redundancy.
The tool set provides comprehensive coverage for contact management, including CRUD operations for contacts, groups, and notes, plus search and event retrieval. Minor gaps include the lack of update/delete operations for contacts and notes, which agents might need to work around, but core workflows are well-supported.