list_automationsThe account's automations — saved searches that re-run on a schedule and export themselves. Shows each one's niche, cities, cadence, destination, whether it's active, when it next runs, and how the last run went.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| count | Yes | ||
| automations | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is established. The description adds meaningful context by explaining what automations are (scheduled searches that export themselves) and what status information is returned. It does not add details like pagination or rate limits, but given the annotation coverage, the bar is met.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that front-loads the core purpose and then provides specific details about returned fields. Every word contributes value, with no redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list tool with no parameters and an existing output schema, the description is complete. It defines the domain concept (automations), states what is listed, and enumerates the output fields, leaving no significant ambiguity about the tool's behavior.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, and the schema is fully covered (100%) by virtue of being empty. The description adds no parameter details because none exist, which matches the baseline expectation for a no-parameter tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly identifies the tool as listing the account's automations (scheduled searches that re-run and export themselves) and enumerates the exact fields shown (niche, cities, cadence, destination, active status, next run, last run). This distinguishes it from sibling list_searches, which likely lists one-off searches.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage context is implied: an agent would use this to inspect scheduled search automations. However, there is no explicit statement about when to choose this over list_searches or other alternatives, nor any exclusions. The definition of automations provides implicit guidance but not direct comparison.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct purpose: search_leads runs live searches while query_leads filters collected leads; create/delete/update_automation form a clear lifecycle; list_* tools target different resources. Descriptions explicitly disambiguate potential overlaps like search/query and list_searches/list_views.
All tool names follow a consistent verb_noun snake_case pattern (e.g., create_automation, list_integrations, export_leads). The verbs are semantically appropriate (get, list, search, query, create, update, delete, enrich, export) and the pattern is uniform throughout.
13 tools is well within the ideal range and covers the full lead-generation workflow without redundancy. Each tool addresses a concrete need, from searching and enrichment to export and automation management.
The tool set covers the entire lifecycle: search_leads and enrich_domains acquire leads, get_search_results and query_leads retrieve them, export_leads pushes them out, and automations re-run searches on schedule. Integration checking and balance are also included, leaving no obvious dead ends or missing essential operations.