Skip to main content
Glama
mambalabsdev

mcp-clay-to-instantly-smartlead-push

by mambalabsdev
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

Server Quality Checklist

75%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v1.0.0

  • Disambiguation5/5

    Only a single tool exists, so there is no possibility of overlapping purposes. The tool's description clarifies it handles both Instantly and Smartlead pushes, but that's a single atomic operation.

    Naming Consistency5/5

    The single tool name follows a clear verb_noun pattern (push_leads_to_sequencer), and with only one tool, there is no inconsistency.

    Tool Count3/5

    At one tool, the server sits at the thin end of the scale. However, the narrow purpose of pushing leads to sequencing vendors justifies a minimal surface, though users may need complementary tools from other servers.

    Completeness5/5

    For its stated purpose of pushing enriched leads to existing campaigns, the tool covers all essential features: mapping, filtering, deduplication, dry run, batching, and detailed reporting. It explicitly does not create campaigns, which is outside its scope.

  • Average 4.7/5 across 1 of 1 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 3 commits in the last 12 weeks
    • Last stable release on
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI is passing

  • This repository is licensed under MIT License.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • This repository includes a glama.json configuration file.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior5/5

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

    The description explicitly discloses write behavior: 'This WRITES to your sequencer campaign unless dry_run is true,' which aligns with readOnlyHint=false. It goes beyond annotations by explaining billing (per lead confirmed created), API key requirements (Instantly v2, Smartlead v1), and dry-run semantics (zero write calls, no charge). This is rich behavioral context with no contradiction to the annotations.

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

    Conciseness4/5

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

    The description is a dense paragraph of about seven sentences, each covering a distinct aspect: purpose, core behavior, return payload, constraints, dry-run, billing, and API specifics. It is logically structured and front-loaded with the main action; while longer than minimal examples, every sentence earns its place for a tool with 10 parameters and no output schema.

    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?

    With no output schema, the description compensates thoroughly by specifying the exact return shape: 'one flat summary row: how many leads were received, dropped... plus the vendor's own error message.' It also covers prerequisites, side effects, billing, and API nuances, making it complete for a complex write tool with 10 parameters and a nested input schema.

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

    Parameters5/5

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

    Even with 100% schema coverage, the description adds significant meaning: it explains parameter precedence ('leads... takes precedence over dataset_id'), the deduplicate API-key requirement on dry runs, and the ICP gate default ('Rows with no icp_score are always kept'). It also clarifies how field_mapping treats unknown targets and how custom_variables pass through, which the schema alone does not convey.

    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 opens with a specific verb and resource: 'Push enriched lead rows into an existing Instantly or Smartlead campaign.' It further details the tool's scope (field mapping, ICP filtering, deduplication, batching) and its flat summary return. Although no sibling tools are listed, the purpose is unambiguous and self-contained.

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

    Usage Guidelines4/5

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

    The description gives concrete usage guidance and prerequisites: 'The campaign must already exist; this does not create campaigns or write sequence copy,' and 'Set dry_run true to get back the exact request payload... the safe way to check a mapping against a new campaign.' It also notes when an API key is needed even on dry_run (deduplicate) and contrasts API versions for Instantly vs Smartlead. It does not list alternative tools, but the provided context is sufficient.

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

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

mcp-clay-to-instantly-smartlead-push MCP server

Copy to your README.md:

Score Badge

mcp-clay-to-instantly-smartlead-push MCP server

Copy to your README.md:

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mambalabsdev/mcp-clay-to-instantly-smartlead-push'

If you have feedback or need assistance with the MCP directory API, please join our Discord server