List the user's Zeekeo Launchpad campaigns (LinkedIn automation). Use this to find a campaign_id for zeekeo_send_message, or call zeekeo_create_campaign to make a new one. Requires the user to have connected their own Zeekeo Launchpad account. Direct them to rankparse.com/dashboard/integrations to connect it.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, destructiveHint, idempotentHint, so safety is covered. The description adds the account-connection requirement and directs users to a specific integration page, which is behavioral context beyond annotations. No 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: first states purpose and usage, second gives requirement and actionable next step. Nothing wasted, front-loaded with the primary purpose.
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 no output schema, the description covers purpose, usage, prerequisite, and a concrete resolution if the prerequisite isn't met. It is complete for agent invocation.
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?
There are zero parameters, so schema coverage is 100% and the description doesn't need to explain any. Per instructions, 0 params = baseline 4, and the description adds no extraneous parameter info, so this is appropriate.
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 clearly specifies 'List the user's Zeekeo Launchpad campaigns (LinkedIn automation)' – a specific verb and resource. It distinguishes from sibling tools like outreach_list_campaigns by naming Zeekeo specifically, and its dual purpose (finding id for send, creating new) is clear.
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: 'Use this to find a campaign_id for zeekeo_send_message, or call zeekeo_create_campaign to make a new one.' Also gives a prerequisite and specific remediation (connecting account via rankparse.com/dashboard/integrations). This is thorough guidance.
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.
The tool set is largely well-disambiguated with clear prefixes (get_, outreach_, zeekeo_) and detailed descriptions for each tool. Some tools like get_site_explorer and get_site_health could be confused at a glance, but their descriptions clearly separate their purposes. Overall, the naming and descriptions prevent meaningful ambiguity.
All tools follow a consistent get_ prefix for data retrieval, with sub-prefixes like get_gsc_, get_page_, and outreach_/zeekeo_ for distinct workflows. There is no mixing of naming conventions (e.g., camelCase) or inconsistent verb usage. The naming pattern is uniform and predictable.
With 63 tools, this server vastly exceeds the typical 3-15 tool scope, categorizing as an extreme overflow. Even for a comprehensive SEO and outreach suite, the sheer number is overwhelming and likely includes redundant or overlapping functionality. This would be confusing for agents and users alike.
The tool set covers a wide range of SEO, backlink analysis, Google Search Console data, and outreach workflows, appearing nearly complete for its stated purpose. However, several tools are marked as 'v1 stub' (e.g., get_internal_links, get_schema_markup), indicating incomplete functionality. Despite these gaps, the overall coverage is extensive and well-rounded.
