Skip to main content
Glama

MisarReach MCP Server

by io.github.Misar-AI

create_lead_list

Create a new, empty lead list in Hunter.io.

Creating the list does not put anything in it, and it does not import anything locally — sync_lead_list does that. Call list_lead_lists first: each call creates a NEW list and nothing deduplicates by name.

Requires an API key and a connected Hunter.io account. Costs no credits. Returns the created list with the id that sync_lead_list needs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesList name (1-200 chars)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already set readOnlyHint=false, idempotentHint=false, etc., but the description adds substantial behavioral context: it clarifies the list is empty, does not import anything locally, each call creates a new list with no name dedup, costs no credits, and returns the created list with the id needed for sync_lead_list. This goes beyond the annotations and gives the agent a full picture.

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?

The description is concise and efficiently front-loaded. The first sentence states the purpose, subsequent sentences clarify side effects, usage sequence, and return value without any fluff. Each sentence contributes essential information, making it model-friendly.

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 low complexity (single param, no output schema) and the presence of sibling tools, the description is complete. It explains the relationship with sync_lead_list and list_lead_lists, prerequisites, costs, and the return value (the id needed by sync_lead_list). No essential context is missing.

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

Parameters3/5

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

The schema covers the only parameter (name) with a clear description ('List name (1-200 chars)') and 100% coverage, so the description doesn't need to add much. The description implies the name is the list's identifier but provides no extra semantics beyond the schema. Baseline of 3 is appropriate.

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 ('Create a new, empty lead list') and the resource ('lead list in Hunter.io'), and distinguishes from siblings by explicitly noting that sync_lead_list handles importing and that each call creates a NEW list with no deduplication. This is a specific verb+resource with clear differentiation.

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?

It gives explicit directives: 'Call list_lead_lists first' and explains that sync_lead_list is the tool for importing, thus telling when to use this tool vs. the alternative. It also mentions requirements (API key, connected account) and provides a critical caveat about no deduplication, offering clear context for usage.

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

All MisarReach MCP Server 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

A4.3/5.0
Disambiguation5/5

Every tool targets a distinct resource and action: deals, leads, lists, autopilot runs, sales agent config, channels, and discovery. Even where tools share an entity, they are clearly differentiated (e.g., list_deals vs get_pipeline, update_deal vs move_deal_stage), with descriptions explicitly calling out when to use which.

Naming Consistency5/5

All 27 tools follow a strict verb_noun snake_case pattern: create, get, list, update, move, search, score, sync, start, submit, verify, etc. No mixed conventions or vague verbs—each name precisely signals its function.

Tool Count3/5

27 tools is on the heavier side and slightly exceeds the typical well-scoped range. However, the server covers multiple subdomains (deals, lead discovery, autopilot, sales agent, channels), so the count is justified by the breadth of the domain, though it feels dense.

Completeness4/5

Core lifecycles are covered: deals (create, list, update, move), leads (search, sync, list, enrich, score, verify, send), autopilot (start, list, status), sales agent (config, actions, process), and channels (status, update). Minor gaps include no delete tool for deals/leads and no stop-autopilot, but these are likely intentional and not blocking.

Resources