Stop a running campaign: sets status to 'stopped' and cancels its pending scheduled actions (a DB trigger marks them skipped). To only pause temporarily, use update_campaign_settings with status='paused'.
| Name | Required | Description | Default |
|---|---|---|---|
| campaign_id | Yes | UUID of the campaign to stop |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds detail beyond annotations: cancels pending scheduled actions via DB trigger. Annotations already indicate destructive and idempotent. Description confirms and elaborates without contradiction.
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?
Two sentences, front-loaded with primary action. No wasted words. Efficient and easy to scan.
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 tool with one parameter and no output schema, the description sufficiently explains the effect (status change, action cancellation) and provides alternative. No gaps.
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 100% with a clear description of campaign_id as UUID. Description does not add additional parameter meaning, meeting baseline for high coverage.
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?
Clear verb ('stop') and resource ('campaign') with specific results: sets status to 'stopped' and cancels pending scheduled actions. Distinguishes from sibling tool update_campaign_settings for pausing.
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?
Explicitly states when to use (to stop a running campaign) and when to use alternative (update_campaign_settings for temporary pause). Also explains the effect on scheduled actions.
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.
Most tools have distinct purposes, but there is some overlap among search tools (search_job_postings, search_google_xray, search_linkedin_people, search_web) and messaging tools (send_connection_request, send_linkedin_message, reply_to_chat). However, detailed descriptions clarify the differences.
All tools follow a consistent verb_noun snake_case pattern (e.g., add_contacts_to_campaign, list_campaigns). No mixing of conventions.
48 tools is high but justifiable given the broad domain (LinkedIn outreach, CRM, campaigns, job postings, etc.). However, some tools could be consolidated (e.g., multiple search tools).
The tool set covers the entire workflow: searching, connecting, messaging, campaign management, CRM operations (fields, stages, tasks, notes), job postings, and posting. No obvious gaps.
