Home

Clay Announcements
Clay Support
Discuss Anything
Feedback & Requests
GTM Career Advice
Introduce Yourself
Member Spotlight
Share Content and Events
Share Full-time Jobs
Share Part Time Jobs
Share Tables, Tools, and Workflows

Community Guidelines

Explore Events
Clay Cup

Powered by Tightknit

Understanding Claygent Tool-Call Constraints Issues | Clay

Understanding Claygent Tool-Call Constraints Issues

·Dec 06, 2025 12:12 AM·

I keep getting responses like this "No website or public-source inspection was performed due to tool-call constraints; defaulted to" when using Claygent. Why is this happening? Whenever it happens, it says tool-call constraints. What is causing this?

6 comments

· Sorted by Oldest

Clay Support
APP
·
·
This "tool-call constraints" message typically happens when Claygent hits processing limitations. The most common causes are network connection issues, usage limits being reached, or overly complex search queries that exceed what Claygent can handle in a single request.
To fix this, try making your search queries more specific and well-defined, break large data requests into smaller batches, and check that your network connection is stable. Also monitor your usage limits and API quotas to make sure you haven't hit any caps.
Are you seeing this error consistently across all your Claygent tasks, or does it happen with specific types of searches?
Clay Support
APP
·
·
If you still need help understanding or resolving the "tool-call constraints" issue with Claygent, I’m here to assist. Would you like to provide more details about the searches or tasks where this happens?
Kierin F.
·
·
Yes what is the best way to test it?
Clay Support
APP
·
·
The best way to test Claygent is using Sandbox Mode - go to your table settings and enable it to create a locked copy with selected test rows. [1] This lets you experiment without burning credits or affecting production data.
You can also use Claygent Builder for risk-free testing - the first 5 test cases are completely free. [2] Build and refine your prompts there, then deploy them to your actual tables once they're working properly.
Start with a few rows, review the output, and make adjustments before running on larger datasets. [3]
Clay Support
APP
·
·
Was that helpful?
Clay Support
APP
·
·
If you need any more help testing Claygent or have questions about the best approach, I’m here to assist. Would you like to share more about what you’re trying to test or any specific challenges you’re facing?