Skip to main content
Glama

MisarReach MCP Server

by io.github.Misar-AI

list_leads

Read-onlyIdempotent

List leads already saved to the account, newest first, with paging and search.

Use this to work with leads you already have. It does NOT find new ones — that is search_leads, which starts a job and costs credits. Narrow to one search job with job_id when you want just that job's results.

Reads only and costs no credits. Requires an API key. Returns saved lead records with contact and company fields plus enrichment and score where present. An empty page is a normal answer, not an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default 1)
limitNoResults per page (default 20, max 100)
job_idNoFilter leads by a specific search job UUID
searchNoSearch term to filter by name, email, or company

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 declare read-only and non-destructive behavior, but the description adds useful context beyond them: costs no credits, requires an API key, returns saved lead records with enrichments and scores, and treats an empty page as normal rather than an error. This fully sets agent expectations.

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 front-loaded with the core purpose, then gives usage guidance, then behavioral notes. Every sentence earns its place, and there is no filler or excessive repetition.

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?

For a read-only list tool with no output schema, the description makes the return contents clear (contact and company fields, enrichment, score) and covers important edge behavior (empty page). With no required parameters and strong annotations, the description is fully sufficient for correct invocation.

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 input schema already provides complete descriptions for all 4 parameters, so the baseline is 3. The description adds general context about paging and the job_id filter but does not materially change or enhance parameter meaning beyond what the schema already states.

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 immediately states 'List leads already saved to the account, newest first, with paging and search', giving a specific verb, resource, scope, and behavior. It also differentiates from search_leads by explicitly saying it does NOT find new leads but rather works with existing ones.

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 clear guidance: 'Use this to work with leads you already have' and explicitly contrasts with search_leads, noting that search starts a job and costs credits. It also instructs when to filter by job_id, making the selection and invocation guidance strong.

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