Skip to main content
Glama
jbalbu01

sales-intelligence

by jbalbu01

Trigger Clay Table Enrichment

clay_trigger_enrichment

Send data to a Clay webhook to trigger a table-based enrichment workflow.

Instructions

Send data to a Clay webhook to trigger a table-based enrichment workflow.

Clay tables run custom enrichment sequences (waterfall emails, phone lookups, intent signals, etc.). The webhook URL is unique to each Clay table — get it from your Clay table settings.

Args:

  • webhook_url (string): The Clay webhook URL for the enrichment table

  • data (object): Key-value pairs to send (e.g. { "email": "john@acme.com", "company": "Acme" })

  • response_format ('markdown' | 'json')

Returns: Confirmation that data was submitted. Enrichment runs asynchronously — results appear in your Clay table.

Examples:

  • Trigger enrichment: webhook_url='https://...', data={"email":"john@acme.com","name":"John Doe"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesKey-value data to send to the webhook (e.g. {email: 'x@y.com', company: 'Acme'})
webhook_urlYesThe Clay webhook URL for the target enrichment table
response_formatNoOutput format: 'markdown' or 'json'markdown
Behavior4/5

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

Annotations already indicate non-read-only, non-idempotent, non-destructive behavior. The description adds valuable context about asynchronous execution ('Enrichment runs asynchronously — results appear in your Clay table') and clarifies that the return is merely a submission confirmation. No contradiction with annotations.

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?

The description is well-structured with a clear opening statement, Args section, Returns note, and Example. Every sentence contributes meaning, and it is concise without being underspecified.

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?

The description covers the core trigger action, asynchronous behavior, prerequisite of obtaining the webhook URL, and return value. It lacks error-handling details or instructions on retrieving results, but these are not essential for a simple trigger tool given the output schema is absent.

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

Parameters3/5

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

Schema description coverage is 100%, so baseline 3 is appropriate. The description lists the same parameter meanings as the schema and provides an example, but adds little beyond what the schema already specifies.

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 clearly states the tool's purpose: 'Send data to a Clay webhook to trigger a table-based enrichment workflow.' It identifies a specific verb, resource, and scope, and distinguishes itself from sibling tools like clay_enrich_person and clay_enrich_company by focusing on table-based enrichment sequences.

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

Usage Guidelines4/5

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

The description provides clear context: it is for table-based enrichment workflows with custom sequences, and notes that the webhook URL is unique to each Clay table. However, it does not explicitly contrast with individual enrichment tools or state when not to use it, so it lacks explicit alternatives/exclusions.

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/jbalbu01/sales-intelligence-mcp-server'

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