sdr_preview_run_nowDry run of the hunter "Run" button. Lists which hunters would run (one source, or every enabled runnable hunter when omitted), flags paid engines and LinkedIn-budget hunters. Nothing runs.
| Name | Required | Description | Default |
|---|---|---|---|
| source | No | Hunter source id; cross_pool and people_pool run automatically and cannot be started by hand | |
| search_id | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / search_id / formatAdded value: +"uuid"Input schema / properties / source / descriptionPrevious value: -"Name of one specific hunter, or omit to run all enabled. E.g. 'linkedin_jobs', 'ai_web_hunter', 'connected_people'."New value: +"Hunter source id; cross_pool and people_pool run automatically and cannot be started by hand"Input schema / properties / source / enumAdded value: +[
+ "linkedin_jobs",
+ "linkedin_company",
+ "linkedin_activity",
+ "ai_web_hunter",
+ "social_signal_hunter",
+ "crunchbase_rss",
+ "hn_hiring",
+ "g2_reviews",
+ "tech_stack",
+ "connected_people",
+ "email_enricher",
+ "linkedin_engagement",
+ "linkedin_job_change",
+ "linkedin_competitor_followers",
+ "github_issues",
+ "adzuna_jobs",
+ "corporate_registries",
+ "web_news_radar",
+ "web_pulse_hunter",
+ "google_places",
+ "web_profile",
+ "local_listings"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden and discloses the key trait: nothing actually runs. It also adds useful operational context by saying it flags paid engines and LinkedIn-budget hunters, though it does not describe permissions or response shape.
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 front-loaded, tight, and every sentence adds value: dry-run purpose, scope/list behavior, flags, and the no-execution guarantee.
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 two-parameter preview tool with no output schema and no annotations, the description gives enough behavioral context to call it correctly. The main remaining gap is that search_id semantics are left entirely to the schema.
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?
Schema coverage is 50%, and the description adds important meaning for the optional source parameter by explaining that omission previews every enabled runnable hunter. However, it does not explain the required search_id parameter, so the schema still carries much of the parameter burden.
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?
The description states a specific verb+resource: it is a dry run of the hunter "Run" button and lists which hunters would run. It clearly distinguishes itself from an actual run by saying "Nothing runs" and explains the source scope.
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?
It clearly frames the tool as a preview/dry-run alternative to actually running hunters, and explains that omitting source previews every enabled runnable hunter. It does not explicitly name the sibling execution tool, but the intended usage context is clear.
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.