Skip to main content
Glama
Sign In

Lyre Leads

by com.lyreleads
OverviewDiscussionsAdmin

Read a search's leads

get_search_results
Read-onlyIdempotent

FREE. Read the leads a search_areas job found, up to 100 per page. Accepts the same filters as the Lyre Leads database, passed as filters, e.g. {"relevanceYes": true, "hasVerifiedEmail": true, "noFBPixel": true}. Each lead comes back compact by default: contact details, business email and its verification state, named contact, relevance verdict with its evidence, software and signals, plus a summary and next steps; detail "full" returns every database field. The summary counts every lead in the search (or every lead the filters match), not only the page, so one read answers how many have emails, contacts or no contact yet; read further pages only when the user asks to see more leads. Enrichment keeps landing for a while after the search finishes, so re-read if leads are still enriching.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 1
limitNoLeads per page (default 50, max 100)
detailNocompact (default) or full (every field, much longer)
job_idYesjob_id returned by search_areas
filtersNoDatabase filter parameters as key/value pairs, e.g. {"relevanceYes": true, "minReviews": 100}

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Leads per page (default 50, max 500)"New value: +"Leads per page (default 50, max 100)"
  2. Changed1 schema field changed
    • addedInput schema / properties / detail
      Added value: +{
+  "description": "compact (default) or full (every field, much longer)",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds real behavioral context on top: it is free, paginated at 100, compact-by-default with a 'full' escape hatch, and the summary reflects the whole search population rather than the page. The note that enrichment continues after the search finishes and requires a re-read is exactly the kind of non-obvious behavior an agent cannot get from structured fields.

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?

Dense but front-loaded: cost, scope, filters, return shape, summary semantics, and enrichment caveat all in one compact block with no filler sentences. It is longer than typical, but each clause carries decision-relevant information.

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 5-parameter tool with a nested filters object and no output schema, the description compensates well: it describes what each lead contains, the difference between compact and full, and how summary counts are scoped. An agent has everything needed to call it and interpret the result.

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 the baseline is 3, but the description goes further: it shows concrete filter keys (hasVerifiedEmail, noFBPixel) not present in the schema example, clarifies that 'full' returns every database field, and explains what the summary counts. Only the page/limit semantics are left entirely to the schema.

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?

States a specific verb and resource ('Read the leads a search_areas job found') and ties the tool to the exact producing sibling, so an agent knows this reads results of a specific job rather than doing the searching itself. Scope ('up to 100 per page') is stated up front.

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?

Gives clear operational guidance: read further pages only when the user asks to see more leads, and re-read while enrichment is still landing. It does not, however, explicitly contrast this tool with siblings like list_results or search_leads, so the routing decision relies on inference.

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

All Lyre Leads toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources