Skip to main content
Glama

rankparse-mcp

by io.github.abhibavishi

zeekeo_create_template

Creates a reusable Zeekeo message template. Call this BEFORE zeekeo_create_campaign — a campaign references templates by the template_id this returns, not inline text. type must be 'linkedin_invite' for a connection-request template, or one of linkedin_message/linkedin_inmail/email_message for a follow-up/reply template. Requires the user to have connected their own Zeekeo Launchpad account. Direct them to rankparse.com/dashboard/integrations to connect it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesMessage text. Supports Zeekeo merge variables like {{FIRST_NAME}} and {{COMPANY}}.
nameYesTemplate name, for your own reference in the Zeekeo dashboard
typeYesWhat kind of message this template is for
subjectNoSubject line, required when type is email_message

TDQS

A4.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare non-read-only, non-destructive, and non-idempotent. The description adds useful contextual behavior: the must-connect-account prerequisite and the template_id return dependency for campaigns. It doesn't contradict annotations, though it could mention side effects of repeated calls, but that's minor given annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences front-load the purpose, provide actionable usage, and include a crucial prerequisite. No fluff or redundant repetition of schema details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (creation with workflow dependency, account requirement, type-specific behavior), the description covers all essential aspects: what it does, when to use it relative to other tools, prerequisites, and type semantics. No output schema is needed since the return value is referenced in context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds extra meaning beyond the schema by explaining the semantic distinction between type values (e.g., 'linkedin_invite' for connection-request vs. others for follow-up/reply), which is not evident from the enum alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Creates a reusable Zeekeo message template') with a specific resource and differentiates from siblings by explicitly referencing the zeekeo_create_campaign workflow and the template_id return.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs to call before zeekeo_create_campaign, explains the relationship, and specifies type usage for different message kinds. Also provides a clear prerequisite (account connection) and a direct URL for setup.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All rankparse-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count1/5

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.

Completeness4/5

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.

Resources